What is the severity of CVE-2020-7968?

CVE-2020-7968 has been classified with high severity due to its incorrect access control vulnerability impacting certain GitLab versions.

How do I fix CVE-2020-7968?

To address CVE-2020-7968, upgrade GitLab to the latest version beyond 12.7.4 or apply patches released by GitLab.

Which GitLab versions are affected by CVE-2020-7968?

CVE-2020-7968 affects GitLab EE versions from 8.0 to 12.7.2, specifically those prior to 12.7.4.

What could happen if CVE-2020-7968 is exploited?

If exploited, CVE-2020-7968 may allow unauthorized access to sensitive data within GitLab applications.

Is CVE-2020-7968 a common vulnerability?

CVE-2020-7968 is notably recognized due to its presence in widely used GitLab versions, making it a significant concern.

Vulnerability/
CVE-2020-7968

high

7.5

CWE

862

5/2/2020

4/8/2024

CVE-2020-7968

First published: Wed Feb 05 2020(Updated: )

GitLab EE 8.0 through 12.7.2 has Incorrect Access Control.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	<12.5.9
GitLab	<12.5.9
GitLab	>=12.6.0<12.6.6
GitLab	>=12.6.0<12.6.6
GitLab	>=12.7.0<12.7.4
GitLab	>=12.7.0<=12.7.4

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-7968?
CVE-2020-7968 has been classified with high severity due to its incorrect access control vulnerability impacting certain GitLab versions.
How do I fix CVE-2020-7968?
To address CVE-2020-7968, upgrade GitLab to the latest version beyond 12.7.4 or apply patches released by GitLab.
Which GitLab versions are affected by CVE-2020-7968?
CVE-2020-7968 affects GitLab EE versions from 8.0 to 12.7.2, specifically those prior to 12.7.4.
What could happen if CVE-2020-7968 is exploited?
If exploited, CVE-2020-7968 may allow unauthorized access to sensitive data within GitLab applications.
Is CVE-2020-7968 a common vulnerability?
CVE-2020-7968 is notably recognized due to its presence in widely used GitLab versions, making it a significant concern.

agent/references
agent/type
agent/author
agent/weakness
agent/severity
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/12.6.0
version/gitlab/12.7.0
version/gitlab/12.7.4

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-7968?
CVE-2020-7968 has been classified with high severity due to its incorrect access control vulnerability impacting certain GitLab versions.
How do I fix CVE-2020-7968?
To address CVE-2020-7968, upgrade GitLab to the latest version beyond 12.7.4 or apply patches released by GitLab.
Which GitLab versions are affected by CVE-2020-7968?
CVE-2020-7968 affects GitLab EE versions from 8.0 to 12.7.2, specifically those prior to 12.7.4.
What could happen if CVE-2020-7968 is exploited?
If exploited, CVE-2020-7968 may allow unauthorized access to sensitive data within GitLab applications.
Is CVE-2020-7968 a common vulnerability?
CVE-2020-7968 is notably recognized due to its presence in widely used GitLab versions, making it a significant concern.