CVE-2020-8113
First published: Fri Mar 06 2020(Updated: )
GitLab 10.7 and later through 12.7.2 has Incorrect Access Control.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=10.7.0<12.6.8 | |
| GitLab | >=10.7.0<12.6.8 | |
| GitLab | >=12.7.0<=12.7.2 | |
| GitLab | >=12.7.0<=12.7.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-8113?
CVE-2020-8113 is classified as a medium severity vulnerability due to incorrect access control.
How do I fix CVE-2020-8113?
To fix CVE-2020-8113, you need to upgrade to GitLab version 12.8 or later.
What versions of GitLab are affected by CVE-2020-8113?
CVE-2020-8113 affects GitLab versions from 10.7 to 12.7.2.
What is the impact of CVE-2020-8113?
The impact of CVE-2020-8113 includes potential unauthorized access to restricted information.
How can I verify if my GitLab installation is vulnerable to CVE-2020-8113?
You can verify your GitLab installation's version against the affected versions listed in the CVE-2020-8113 report.
- agent/type
- agent/references
- agent/weakness
- agent/author
- agent/severity
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/10.7.0
- version/gitlab/12.7.0
- version/gitlab/12.7.2