# CVE-2022-4331: Auth bypass in GitLab

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

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N`)
- **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:** Yes
- **Published:** 9 Mar 2023
- **Updated:** 28 Feb 2025
- **Also known as:** BIT-gitlab-2022-4331, GHSA-fh7h-m5x3-9v4g

## 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 (Improper Access Control)

## Which versions are affected by CVE-2022-4331?

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


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

Products: 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.

## Is CVE-2022-4331 being exploited?

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

## Other vulnerabilities in Gitlab Gitlab

- [CVE-2026-97229](https://insights.sbomify.com/CVE-2026-97229/): GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound (critical 10.0, exploited in the wild)
- [CVE-2026-85706](https://insights.sbomify.com/CVE-2026-85706/): GitLab Community Edition and Enterprise Edition Path Traversal (critical 10.0, exploited in the wild)
- [CVE-2023-7028](https://insights.sbomify.com/CVE-2023-7028/): GitLab Community and Enterprise Editions Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2021-22205](https://insights.sbomify.com/CVE-2021-22205/): GitLab Community and Enterprise Editions Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2021-39935](https://insights.sbomify.com/CVE-2021-39935/): GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) (medium 6.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4331 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4331 exists.

Affected packages and fixed versions:
- gitlab (Bitnami): affected from 15.1.0; fixed in 15.7.8, 15.8.4, 15.9.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-4331/ (Markdown: https://insights.sbomify.com/CVE-2022-4331/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-4331
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-4331
- OSV: https://osv.dev/vulnerability/CVE-2022-4331

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-4331/
Summaries are generated and may contain mistakes; the official description above is the record.