Remote code execution via unsanitized Git paths
Published Mar 29, 2021 · Updated Aug 3, 2024
Path traversal in gitjacker before 0.1.0 allows remote attackers to execute arbitrary code via a crafted remote .git directory. The downloadFile routine joined remotely supplied Git paths into the reconstructed .git tree without confining them, then Git reset and checkout consumed that tree. Exploitation requires gitjacker to process attacker-controlled Git metadata, and resulting commands run with the gitjacker process's privileges.
Summary
What happened
Path traversal in gitjacker before 0.1.0 allows remote attackers to execute arbitrary code via a crafted remote .git directory. The downloadFile routine joined remotely supplied Git paths into the reconstructed .git tree without confining them, then Git reset and checkout consumed that tree. Exploitation requires gitjacker to process attacker-controlled Git metadata, and resulting commands run with the gitjacker process's privileges.
The record
- CVE
- CVE-2021-29417
- Published
- Mar 29, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 29, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
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