What is the severity of CVE-2020-10079?

CVE-2020-10079 has been classified as a high-severity vulnerability due to incorrect access control in GitLab.

How do I fix CVE-2020-10079?

To fix CVE-2020-10079, you should upgrade your GitLab instance to version 12.8.2 or later where the issue has been addressed.

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

CVE-2020-10079 affects GitLab versions from 7.10 through 12.8.1.

What type of vulnerability is CVE-2020-10079?

CVE-2020-10079 is an access control vulnerability that impacts user authentication.

What are the potential impacts of CVE-2020-10079?

The potential impact of CVE-2020-10079 includes unauthorized access for users who should be required to enable two-factor authentication.

Vulnerability/
CVE-2020-10079

medium

5.3

CWE

306

13/3/2020

4/8/2024

CVE-2020-10079

First published: Fri Mar 13 2020(Updated: )

GitLab 7.10 through 12.8.1 has Incorrect Access Control. Under certain conditions where users should have been required to configure two-factor authentication, it was not being required.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=7.10.0<=12.8.1
GitLab	>=7.10.0<=12.8.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-10079?
CVE-2020-10079 has been classified as a high-severity vulnerability due to incorrect access control in GitLab.
How do I fix CVE-2020-10079?
To fix CVE-2020-10079, you should upgrade your GitLab instance to version 12.8.2 or later where the issue has been addressed.
Which versions of GitLab are affected by CVE-2020-10079?
CVE-2020-10079 affects GitLab versions from 7.10 through 12.8.1.
What type of vulnerability is CVE-2020-10079?
CVE-2020-10079 is an access control vulnerability that impacts user authentication.
What are the potential impacts of CVE-2020-10079?
The potential impact of CVE-2020-10079 includes unauthorized access for users who should be required to enable two-factor authentication.

agent/references
agent/type
agent/severity
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
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/7.10.0
version/gitlab/12.8.1

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-10079?
CVE-2020-10079 has been classified as a high-severity vulnerability due to incorrect access control in GitLab.
How do I fix CVE-2020-10079?
To fix CVE-2020-10079, you should upgrade your GitLab instance to version 12.8.2 or later where the issue has been addressed.
Which versions of GitLab are affected by CVE-2020-10079?
CVE-2020-10079 affects GitLab versions from 7.10 through 12.8.1.
What type of vulnerability is CVE-2020-10079?
CVE-2020-10079 is an access control vulnerability that impacts user authentication.
What are the potential impacts of CVE-2020-10079?
The potential impact of CVE-2020-10079 includes unauthorized access for users who should be required to enable two-factor authentication.