CVE-2022-4331 Auth bypass in GitLab

Medium 5.7 Published 9 Mar 2023 Updated 28 Feb 2025

Removed malicious maintainers can regain access to transferred SAML-enabled groups via SSO or SCIM tokens, allowing unauthorized actions.

Exploited in the wild: Not known
Login needed: An administrator
Attackable: Over the internet
Victim action needed: A user has to click or open something
Fix: Available

What is CVE-2022-4331?

CVE-2022-4331 is a medium-severity authentication bypass vulnerability in Gitlab Gitlab, published on 9 Mar 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

Official description

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.

Weakness: CWE-284

Which versions are affected by CVE-2022-4331?

1 open source package ship an affected version, including gitlab. It affects 1 product.

Package	Affected	Fixed in
`gitlab` Bitnami	From `15.1.0`	`15.7.8, 15.8.4, 15.9.2`

Products include Gitlab Gitlab.

How do I fix CVE-2022-4331?

Upgrade gitlab to a fixed version for your release line: 15.7.8, 15.8.4 or 15.9.2.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2022-4331 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4331 exists.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2022-4331, GHSA-fh7h-m5x3-9v4g.