CVE-2020-13272 Auth bypass in GitLab
Attackers can bypass OAuth verification checks to use authorization code flows, potentially leading to unauthorized access or account takeover in GitLab.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2020-13272?
CVE-2020-13272 is a high-severity authentication bypass vulnerability in Gitlab Gitlab, published on 19 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
OAuth flow missing verification checks CE/EE 12.3 and later through 13.0.1 allows unverified user to use OAuth authorization code flow
Weakness: CWE-345
Which versions are affected by CVE-2020-13272?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 12.3.0 | 12.9.8, 12.10.7, 13.0.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2020-13272?
Upgrade gitlab to a fixed version for your release line: 12.9.8, 12.10.7 or 13.0.1.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2020-13272 being exploited?
There is no known exploitation of CVE-2020-13272 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-2020-13272, GHSA-jmw9-579m-cw2x.