Code execution via unchecked checkout paths
Published May 23, 2024 · Updated Aug 2, 2024
Relative path traversal in GitoxideLabs gitoxide before 0.36.0 allows remote attackers to write files outside a cloned working tree. The gix-worktree-state checkout path accepts crafted tree or blob names without confirming that the resolved destination remains inside the worktree. Exploitation requires cloning an untrusted repository; crafted .git paths can install hooks that later execute with the cloning user's privileges.
Summary
What happened
Relative path traversal in GitoxideLabs gitoxide before 0.36.0 allows remote attackers to write files outside a cloned working tree. The gix-worktree-state checkout path accepts crafted tree or blob names without confirming that the resolved destination remains inside the worktree. Exploitation requires cloning an untrusted repository; crafted .git paths can install hooks that later execute with the cloning user's privileges.
The record
- CVE
- CVE-2024-35186
- Published
- May 23, 2024
- Updated
- Aug 2, 2024
- Vendor
- GitoxideLabs
- Product
- gitoxide
- Classifications
- CWE-23, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 23, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=0 <0.36.0
- Affected versionversion=< 0.36.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Upstream crafted-repository checkout proof of conceptproof of concept · demonstrated
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