CVE-2020-10074
First published: Fri Mar 13 2020(Updated: )
GitLab 10.1 through 12.8.1 has Incorrect Access Control. A scenario was discovered in which a GitLab account could be taken over through an expired link.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=10.1.0<=12.8.1 | |
| GitLab | >=10.1.0<=12.8.1 |
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-10074?
CVE-2020-10074 has a moderate severity level due to the potential for GitLab account takeover.
How do I fix CVE-2020-10074?
To fix CVE-2020-10074, upgrade your GitLab instance to version 12.8.2 or later.
Which versions of GitLab are affected by CVE-2020-10074?
CVE-2020-10074 affects GitLab versions from 10.1 through 12.8.1.
What type of vulnerability is CVE-2020-10074?
CVE-2020-10074 is classified as an Incorrect Access Control vulnerability.
What is the potential impact of CVE-2020-10074?
The potential impact of CVE-2020-10074 is that a malicious user could take over a GitLab account via an expired link.
- agent/references
- agent/type
- agent/severity
- 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/10.1.0
- version/gitlab/12.8.1