CVE-2020-13303: High severity gitlab vulnerability
Published Sep 15, 2020
·Updated
A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. Due to improper verification of permissions, an unauthorized user can access a private repository within a public project.
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 15, 2020
CVE Published
via MITRE·12:27 PM
Data Sourced
via MITRE·12:27 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-13303?
CVE-2020-13303 has a medium severity rating due to improper permission verification allowing unauthorized access to private repositories.
2
How do I fix CVE-2020-13303?
To fix CVE-2020-13303, upgrade GitLab to version 13.1.10, 13.2.8, or 13.3.4 or later.
3
Which GitLab versions are affected by CVE-2020-13303?
CVE-2020-13303 affects GitLab versions before 13.1.10, 13.2.8, and 13.3.4.
4
Can unauthorized users access private repositories due to CVE-2020-13303?
Yes, CVE-2020-13303 allows unauthorized users to access private repositories within publicly accessible projects.
5
Is there a patch available for CVE-2020-13303?
Yes, the patch for CVE-2020-13303 is included in the GitLab versions 13.1.10, 13.2.8, and 13.3.4.