CVE-2020-13265: Medium severity gitlab vulnerability
Published Jun 19, 2020
·Updated
User email verification bypass in GitLab CE/EE 12.5 and later through 13.0.1 allows user to bypass email verification
Affected Software
6 affected components
GitLab GitLab>=12.5.0<12.9.8
GitLab GitLab>=12.5.0<12.9.8
GitLab GitLab>=12.10.0<12.10.7
GitLab GitLab>=12.10.0<12.10.7
GitLab GitLab=13.0.0
GitLab GitLab=13.0.0
Event History
Jun 19, 2020
CVE Published
via MITRE·09:42 PM
Data Sourced
via MITRE·09:42 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-13265?
CVE-2020-13265 is classified as a high severity vulnerability due to the potential for unauthorized access.
2
How do I fix CVE-2020-13265?
To fix CVE-2020-13265, upgrade GitLab to the latest version that has addressed this vulnerability.
3
Which versions of GitLab are affected by CVE-2020-13265?
CVE-2020-13265 affects GitLab versions from 12.5.0 to 12.9.8 and 12.10.0 to 12.10.7, including version 13.0.0.
4
What impact does CVE-2020-13265 have on user accounts?
CVE-2020-13265 allows users to bypass email verification, potentially leading to unauthorized account access.
5
Is CVE-2020-13265 present in both GitLab CE and EE?
Yes, CVE-2020-13265 is present in both GitLab Community Edition (CE) and GitLab Enterprise Edition (EE) versions.