CVE-2020-13322: High severity gitlab vulnerability
Published Sep 29, 2020
·Updated
A vulnerability was discovered in GitLab versions after 12.9. Due to improper verification of permissions, an unauthorized user can create and delete deploy tokens.
Affected Software
3 affected components
GitLab GitLab>=12.9.0<12.10.13
GitLab GitLab>=13.0.0<13.0.8
GitLab GitLab>=13.1.0<13.1.2
Event History
Sep 29, 2020
CVE Published
via MITRE·04:01 PM
Data Sourced
via MITRE·04:01 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-13322?
CVE-2020-13322 has a severity rating of medium due to its potential for unauthorized access.
2
How do I fix CVE-2020-13322?
To fix CVE-2020-13322, upgrade GitLab to version 12.10.13 or later, or to version 13.0.8 or later, or to version 13.1.2 or later.
3
What versions are affected by CVE-2020-13322?
CVE-2020-13322 affects GitLab versions from 12.9.0 to 12.10.13, 13.0.0 to 13.0.8, and 13.1.0 to 13.1.2.
4
What type of vulnerability is CVE-2020-13322?
CVE-2020-13322 is a permission verification vulnerability that allows unauthorized users to manage deploy tokens.
5
Can CVE-2020-13322 lead to data breaches?
Yes, CVE-2020-13322 can lead to data breaches if an unauthorized user exploits the vulnerability to control deploy tokens.