CVE-2020-13293: High severity gitlab vulnerability
Published 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.
Affected Software
3 affected components
GitLab GitLab>=1.0.0<13.0.12
GitLab GitLab>=13.1.0<13.1.6
GitLab GitLab>=13.2.0<13.2.3
Event History
Aug 10, 2020
CVE Published
via MITRE·01:28 PM
Data Sourced
via MITRE·01:28 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-13293?
CVE-2020-13293 is considered a medium severity vulnerability affecting specific versions of GitLab.
2
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.
3
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.
4
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.
5
Has CVE-2020-13293 been publicly disclosed?
Yes, CVE-2020-13293 has been publicly disclosed and affects multiple versions of GitLab.