CVE-2020-13292 Auth bypass in GitLab
Attackers can bypass email verification requirements in the OAuth flow, potentially gaining unauthorized access to GitLab accounts.
- 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-13292?
CVE-2020-13292 is a critical authentication bypass vulnerability in Gitlab Gitlab, published on 10 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
In GitLab before 13.0.12, 13.1.6 and 13.2.3, it is possible to bypass E-mail verification which is required for OAuth Flow.
Weakness: CWE-287
Which versions are affected by CVE-2020-13292?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 12.3.0 | 13.0.12, 13.1.6, 13.2.3 |
Products include Gitlab Gitlab.
How do I fix CVE-2020-13292?
Upgrade gitlab to a fixed version for your release line: 13.0.12, 13.1.6 or 13.2.3.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2020-13292 being exploited?
There is no known exploitation of CVE-2020-13292 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-13292, GHSA-35pq-fvh7-h49r, UBUNTU-CVE-2020-13292.