CVE-2021-22237 Auth bypass in GitLab
GitLab allows impersonation token users to perform Git actions even when impersonation is disabled, bypassing security controls.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2021-22237?
CVE-2021-22237 is a medium-severity authentication bypass vulnerability in Gitlab Gitlab, published on 25 Aug 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
Under specialized conditions, GitLab may allow a user with an impersonation token to perform Git actions even if impersonation is disabled. This vulnerability is present in GitLab CE/EE versions before 13.12.9, 14.0.7, 14.1.2
Weakness: CWE-384
Which versions are affected by CVE-2021-22237?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 13.1.0 | 13.12.9, 14.0.7, 14.1.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2021-22237?
Upgrade gitlab to a fixed version for your release line: 13.12.9, 14.0.7 or 14.1.2.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2021-22237 being exploited?
There is no known exploitation of CVE-2021-22237 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2021-22237, GHSA-p3jh-342h-w8hj, UBUNTU-CVE-2021-22237.