Repository privilege escalation via path traversal
Published Jan 28, 2020 · Updated Aug 6, 2024
Privilege escalation in GitLab 5.0 through 5.4.1 allows remote authenticated users to clone arbitrary repositories via Git SSH. The parse_cmd function in lib/gitlab_shell.rb copies the SSH repository argument without validating that it remains under the configured repositories root, allowing path traversal to another repository. An authenticated GitLab user with an SSH key can exploit this to bypass repository authorization and read repository contents; no service interruption is described.
Summary
What happened
Privilege escalation in GitLab 5.0 through 5.4.1 allows remote authenticated users to clone arbitrary repositories via Git SSH. The parse_cmd function in lib/gitlab_shell.rb copies the SSH repository argument without validating that it remains under the configured repositories root, allowing path traversal to another repository. An authenticated GitLab user with an SSH key can exploit this to bypass repository authorization and read repository contents; no service interruption is described.
The record
- CVE
- CVE-2013-4583
- Published
- Jan 28, 2020
- Updated
- Aug 6, 2024
- Vendor
- GitLab
- Product
- GitLab Shell
- Classifications
- CWE-269, T1006
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 28, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=before 1.7.8
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo