Learn about CVE-2022-4331 affecting GitLab EE versions 15.1 to 15.9.2, allowing unauthorized access to groups with SAML SSO enabled. Follow mitigation steps.
An issue has been discovered in GitLab EE affecting all versions starting from 15.1 before 15.7.8, all versions starting from 15.8 before 15.8.4, all versions starting from 15.9 before 15.9.2. If a group with SAML SSO enabled is transferred to a new namespace as a child group, it's possible previously removed malicious maintainer or owner of the child group can still gain access to the group via SSO or a SCIM token to perform actions on the group.
Understanding CVE-2022-4331
This section provides details about the CVE-2022-4331 vulnerability in GitLab EE.
What is CVE-2022-4331?
CVE-2022-4331 is a vulnerability in GitLab EE that allows a previously removed malicious user to gain unauthorized access to a group with SAML SSO enabled.
The Impact of CVE-2022-4331
The impact of CVE-2022-4331 includes unauthorized access by a removed user, potentially leading to security breaches and unauthorized actions within the affected group.
Technical Details of CVE-2022-4331
This section outlines the technical details of the CVE-2022-4331 vulnerability.
Vulnerability Description
The vulnerability arises from improper access control in GitLab EE, specifically related to the transfer of groups with SAML SSO enabled to new namespaces.
Affected Systems and Versions
GitLab EE versions starting from 15.1 before 15.7.8, 15.8 before 15.8.4, and 15.9 before 15.9.2 are affected by this vulnerability.
Exploitation Mechanism
A previously removed malicious maintainer or owner of a child group can exploit this vulnerability to gain access to the group via SSO or a SCIM token.
Mitigation and Prevention
To address CVE-2022-4331, organizations can take the following steps.
Immediate Steps to Take
Long-Term Security Practices
Patching and Updates
Stay informed about security updates and patches released by GitLab, and promptly apply them to ensure the security of your GitLab EE instance.