CVE-2020-13313: 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. An unauthorized project maintainer could edit the subgroup badges due to the lack of authorization control.
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·07:40 PM
Data Sourced
via MITRE·07:40 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-13313?
CVE-2020-13313 has a medium severity rating due to the unauthorized modification of subgroup badges.
2
How do I fix CVE-2020-13313?
To fix CVE-2020-13313, upgrade GitLab to version 13.1.10 or later, 13.2.8 or later, or 13.3.4 or later.
3
What versions of GitLab are affected by CVE-2020-13313?
CVE-2020-13313 affects GitLab versions prior to 13.1.10, 13.2.8, and 13.3.4.
4
Who can exploit CVE-2020-13313?
An unauthorized project maintainer can exploit CVE-2020-13313 to modify subgroup badges.
5
Is CVE-2020-13313 a critical vulnerability?
CVE-2020-13313 is not classified as critical, but it can lead to unauthorized changes in project settings.