CVE-2020-13316

Description

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.

5.4

CVSS

Severity: Medium

CVSS 3.1 •

CVSS 2.0 •

EPSS 0.15%

Vendor Advisory gitlab.com

Affected: GitLab GitLab

References

Link	Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/220137	broken link
https://hackerone.com/reports/884174	third party advisory permissions required
https://gitlab.com/gitlab-org/cves/-/blob/master/2020/CVE-2020-13316.json	vendor advisory

Frequently Asked Questions

What is the severity of CVE-2020-13316?: CVE-2020-13316 has been scored as a medium severity vulnerability.
How to fix CVE-2020-13316?: To fix CVE-2020-13316, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-13316 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2020-13316 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-13316?: CVE-2020-13316 affects GitLab GitLab.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.