CVE-2020-10977 Path traversal in n/a
Attackers can exploit a path traversal vulnerability in GitLab when moving issues between projects to access or modify unauthorized files.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2020-10977?
CVE-2020-10977 is a medium-severity path traversal vulnerability in Gitlab Gitlab, published on 8 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
GitLab EE/CE 8.5 to 12.9 is vulnerable to a an path traversal when moving an issue between projects.
Weakness: CWE-22
Which versions are affected by CVE-2020-10977?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 8.5.0 | 12.9.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2020-10977?
Upgrade gitlab to 12.9.1 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2020-10977 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-10977 exists.
Public exploit code: 1 Metasploit module and 8 proofs of concept on GitHub.
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-10977, GHSA-9cwr-gv28-fqcw, UBUNTU-CVE-2020-10977.