CVE-2020-13292

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.

Category

9.6
CVSS
Severity: Critical
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.12%
Third-Party Advisory gitlab.com Third-Party Advisory hackerone.com
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/228629 broken link
https://hackerone.com/reports/922456 third party advisory permissions required
https://gitlab.com/gitlab-org/cves/-/blob/master/2020/CVE-2020-13292.json third party advisory

Frequently Asked Questions

What is the severity of CVE-2020-13292?
CVE-2020-13292 has been scored as a critical severity vulnerability.
How to fix CVE-2020-13292?
To fix CVE-2020-13292, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-13292 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-13292 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-13292?
CVE-2020-13292 affects GitLab GitLab.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.