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.

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.

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.

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.

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.

Vulnerability/
CVE-2020-13292

critical

9.6

CWE

287

10/8/2020

4/8/2024

CVE-2020-13292

First published: Mon 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.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.3.0<13.0.12
GitLab	>=13.1.0<13.1.6
GitLab	>=13.2.0<13.2.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

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.
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.
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.
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.
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.

agent/type
agent/references
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/12.3.0
version/gitlab/13.1.0
version/gitlab/13.2.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

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.
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.
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.
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.
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.