CVE-2020-13316: Medium severity gitlab vulnerability
Published Sep 14, 2020
·Updated
A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. GitLab was not validating a Deploy-Token and allowed a disabled repository be accessible via a git command line.
Affected Software
6 affected components
GitLab GitLab>=13.1.0<13.1.10
GitLab GitLab>=13.1.0<13.1.10
GitLab GitLab>=13.2.0<13.2.8
GitLab GitLab>=13.2.0<13.2.8
GitLab GitLab>=13.3.0<13.3.4
GitLab GitLab>=13.3.0<13.3.4
Event History
Sep 14, 2020
CVE Published
via MITRE·06:41 PM
Data Sourced
via MITRE·06:41 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-13316?
CVE-2020-13316 has a medium severity rating due to its potential to allow unauthorized access to disabled repositories.
2
How do I fix CVE-2020-13316?
To fix CVE-2020-13316, upgrade your GitLab installation to version 13.1.10, 13.2.8, or 13.3.4 or later.
3
Which versions of GitLab are affected by CVE-2020-13316?
CVE-2020-13316 affects GitLab versions prior to 13.1.10, 13.2.8, and 13.3.4.
4
What kind of vulnerability is CVE-2020-13316?
CVE-2020-13316 is a security vulnerability related to improper validation of Deploy-Tokens.
5
Can I still access my repositories if I have CVE-2020-13316?
Yes, if you are using an affected version, your disabled repositories may still be accessible via the git command line.