CVE-2020-13316 Missing authorization in GitLab
Attackers can access disabled repositories via git commands due to missing deploy token validation in GitLab.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2020-13316?
CVE-2020-13316 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 14 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Which versions are affected by CVE-2020-13316?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 1.0.0 | 13.1.10, 13.2.8, 13.3.4 |
Products include Gitlab Gitlab.
How do I fix CVE-2020-13316?
Upgrade gitlab to a fixed version for your release line: 13.1.10, 13.2.8 or 13.3.4.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2020-13316 being exploited?
There is no known exploitation of CVE-2020-13316 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2020-13316, GHSA-x8mp-jv75-5hrp, UBUNTU-CVE-2020-13316.