CVE-2020-7968: High severity GitLab GitLab vulnerability
Published Feb 5, 2020
·Updated
GitLab EE 8.0 through 12.7.2 has Incorrect Access Control.
Affected Software
6 affected components
GitLab GitLab<12.5.9
GitLab GitLab<12.5.9
GitLab GitLab>=12.6.0<12.6.6
GitLab GitLab>=12.6.0<12.6.6
GitLab GitLab>=12.7.0<12.7.4
GitLab GitLab>=12.7.0<=12.7.4
Event History
Feb 5, 2020
CVE Published
via MITRE·03:56 PM
Data Sourced
via MITRE·03:56 PM
Description
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
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.
2
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.
3
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.
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.
5
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.