CVE-2020-13293
First published: Mon Aug 10 2020(Updated: )
In GitLab before 13.0.12, 13.1.6 and 13.2.3 using a branch with a hexadecimal name could override an existing hash.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=1.0.0<13.0.12 | |
| GitLab | >=13.1.0<13.1.6 | |
| GitLab | >=13.2.0<13.2.3 |
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-13293?
CVE-2020-13293 is considered a medium severity vulnerability affecting specific versions of GitLab.
How do I fix CVE-2020-13293?
To fix CVE-2020-13293, upgrade GitLab to version 13.0.12, 13.1.6, or 13.2.3 or later.
What versions of GitLab are affected by CVE-2020-13293?
CVE-2020-13293 affects GitLab versions prior to 13.0.12, 13.1.6, and 13.2.3.
What does CVE-2020-13293 exploit?
CVE-2020-13293 exploits the ability to use a branch with a hexadecimal name that can override an existing hash.
Has CVE-2020-13293 been publicly disclosed?
Yes, CVE-2020-13293 has been publicly disclosed and affects multiple versions of GitLab.
- agent/type
- agent/references
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/severity
- 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/1.0.0
- version/gitlab/13.1.0
- version/gitlab/13.2.0