What is the severity of CVE-2020-13297?

CVE-2020-13297 has been classified as a high-severity vulnerability due to its potential to bypass two-factor authentication in GitLab.

Which versions of GitLab are affected by CVE-2020-13297?

CVE-2020-13297 affects GitLab versions before 13.1.10, 13.2.8, and 13.3.4.

How do I fix CVE-2020-13297?

To fix CVE-2020-13297, upgrade your GitLab installation to versions 13.1.10, 13.2.8, or 13.3.4 or later.

What type of attack does CVE-2020-13297 allow?

CVE-2020-13297 allows a malicious user to bypass the two-factor authentication for groups through a specific API query.

Is two-factor authentication secure in the affected versions of GitLab?

In GitLab versions affected by CVE-2020-13297, two-factor authentication can be compromised, making it less secure.

Vulnerability/
CVE-2020-13297

medium

5.4

14/9/2020

4/8/2024

CVE-2020-13297

First published: Mon Sep 14 2020(Updated: )

A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. When 2 factor authentication was enabled for groups, a malicious user could bypass that restriction by sending a specific query to the API endpoint.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	<13.1.10
GitLab	>=13.2.0<13.2.8
GitLab	>=13.3.0<13.3.4

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-13297?
CVE-2020-13297 has been classified as a high-severity vulnerability due to its potential to bypass two-factor authentication in GitLab.
Which versions of GitLab are affected by CVE-2020-13297?
CVE-2020-13297 affects GitLab versions before 13.1.10, 13.2.8, and 13.3.4.
How do I fix CVE-2020-13297?
To fix CVE-2020-13297, upgrade your GitLab installation to versions 13.1.10, 13.2.8, or 13.3.4 or later.
What type of attack does CVE-2020-13297 allow?
CVE-2020-13297 allows a malicious user to bypass the two-factor authentication for groups through a specific API query.
Is two-factor authentication secure in the affected versions of GitLab?
In GitLab versions affected by CVE-2020-13297, two-factor authentication can be compromised, making it less secure.

agent/type
agent/references
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/13.2.0
version/gitlab/13.3.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-13297?
CVE-2020-13297 has been classified as a high-severity vulnerability due to its potential to bypass two-factor authentication in GitLab.
Which versions of GitLab are affected by CVE-2020-13297?
CVE-2020-13297 affects GitLab versions before 13.1.10, 13.2.8, and 13.3.4.
How do I fix CVE-2020-13297?
To fix CVE-2020-13297, upgrade your GitLab installation to versions 13.1.10, 13.2.8, or 13.3.4 or later.
What type of attack does CVE-2020-13297 allow?
CVE-2020-13297 allows a malicious user to bypass the two-factor authentication for groups through a specific API query.
Is two-factor authentication secure in the affected versions of GitLab?
In GitLab versions affected by CVE-2020-13297, two-factor authentication can be compromised, making it less secure.