ADVISORY!

TLP : CLEAR

Date : 02/05/2024

REF NO : CERT / 2024/05/38

GitLab Multiple Vulnerabilities

Severity Level: High

Components Affected

  • GitLab Community Edition (CE) versions prior to 16.7.2, 16.6.4 and 16.5.6
  • GitLab Enterprise Edition (EE) versions prior to 16.7.2, 16.6.4 and 16.5.6

Overview

Multiple vulnerabilities were identified in GitLab. A remote attacker could exploit some of these vulnerabilities to trigger data manipulation, elevation of privilege and security restriction bypass on the targeted system.

 

Description

Multiple issues have been discovered in GitLab CE/EE, affecting various versions. A vulnerability in all versions from 12.2 to 16.5.6, 16.6 to 16.6.4, and 16.7 to 16.7.2 allows attackers to potentially modify signed commit metadata. Another issue in GitLab EE, from versions 15.3 to 16.5.6, 16.6 to 16.6.4, and 16.7 to 16.7.2, permits bypassing required CODEOWNERS approval by adding changes to an approved merge request. Incorrect authorization checks from versions 8.13 to 16.5.6, 16.6 to 16.6.4, and 16.7 to 16.7.2 enable abuse of slack/mattermost integrations to execute slash commands as another user. An improper access control vulnerability in GitLab Remote Development, affecting all versions before 16.5.6, 16.6 to 16.6.4, and 16.7 to 16.7.2, allows attackers to create a workspace in one group associated with an agent from another group. Additionally, in versions 16.1 to 16.7.2, user account password reset emails could be sent to unverified email addresses.

Impact

  • Security Restriction Bypass
  • Data Manipulation
  • Elevation of Privilege

Solution/ Workarounds

Before installation of the software, please visit the vendor web-site for more details.

Apply fixes issued by the vendor:

Reference

Disclaimer : The information provided herein is on an “as is” basis, without warranty of any kind.

Sri Lanka Computer Emergency Readiness Team | Coordination Centre

Copyright © 2023 SRI LANKA CERT | CC