CVE-2020-13292: Critical severity gitlab vulnerability
Published Aug 10, 2020
·Updated
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.
Affected Software
3 affected components
GitLab GitLab>=12.3.0<13.0.12
GitLab GitLab>=13.1.0<13.1.6
GitLab GitLab>=13.2.0<13.2.3
Event History
Aug 10, 2020
CVE Published
via MITRE·01:33 PM
Data Sourced
via MITRE·01:33 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-13292?
CVE-2020-13292 has been assigned a medium severity rating due to its potential to bypass email verification during the OAuth flow.
2
How do I fix CVE-2020-13292?
To fix CVE-2020-13292, upgrade GitLab to version 13.0.12, 13.1.6, or 13.2.3 or later.
3
Which GitLab versions are affected by CVE-2020-13292?
CVE-2020-13292 affects GitLab versions prior to 13.0.12, 13.1.6, and 13.2.3.
4
What impact does CVE-2020-13292 have on user accounts?
CVE-2020-13292 allows attackers to bypass email verification, potentially enabling unauthorized access to user accounts.
5
Is authentication compromised due to CVE-2020-13292?
Yes, CVE-2020-13292 compromises the authentication process by allowing users to authenticate via OAuth without verifying their email.