DevOps platform GitLab has announced security updates that resolve multiple vulnerabilities, including a critical-severity bug leading to account takeover.
Tracked as CVE-2022-1680 (CVSS score of 9.9), the security issue was identified in GitLab Enterprise Edition (EE) and it affects all versions from 11.10 before 14.9.5, from 14.10 before 14.10.4, and from 15.0 before 15.0.1.
“When group SAML SSO is configured, the SCIM feature (available only on Premium+ subscriptions) may allow any owner of a Premium group to invite arbitrary users through their username and email, then change those users’ email addresses via SCIM to an attacker-controlled email address,” GitLab explains.
Thus, should no two-factor authentication option be enabled on the impacted accounts, such actions would result in the attacker taking them over. The attacker would then be able to change the display name and username of the accounts.
The platform recommends that self-managed administrators check whether group_saml is enabled on their deployments. The Configuring Group SAML on a self-managed GitLab instance documentation provides further information on this.
GitLab says it has also addressed two high-severity flaws in GitLab EE and GitLab Community Edition (CE).
Tracked as CVE-2022-1940 (CVSS score of 7.7), the first of these issues is described as a cross-site scripting (XSS) in GitLab EE’s Jira integration, which could allow an attacker to craft Jira issues and achieve arbitrary JavaScript code execution.
The second of these issues was assigned the identifier CVE-2022-1948 (CVSS score of 8.7) and is described as an XSS resulting from a missing input validation in quick actions, which could allow an attacker to inject HTML code in contact details.
GitLab also announced that it has addressed four medium-severity flaws and one low-severity bug with the release of versions 15.0.1, 14.10.4, and 14.9.5 of GitLab CE and GitLab EE.
“These versions contain important security fixes, and we strongly recommend that all GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version,” the platform said.
Related: GitLab Patches Critical Account Takeover Vulnerability
Related: Many GitLab Servers Affected by Actively Exploited Flaw Patched Six Months Ago