gix traversal outside working tree enables arbitrary code execution
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.36.0, 0.11.0, 0.33.0, 0.34.0, 0.63.0, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
gitoxide is a pure Rust implementation of Git. During checkout, `gix-worktree-state` does not verify that paths point to locations in the working tree. A specially crafted repository can, when cloned, place new files anywhere writable by the application. This vulnerability leads to a major loss of confidentiality, integrity, and availability, but creating files outside a working tree without attempting to execute code can directly impact integrity as well. This vulnerability has been patched in version(s) 0.36.0.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Byron gitoxide
fixed in 0.36.0
- gix-fscrates.io
From 0.0.0-0 · fixed in 0.11.0
- gix-indexcrates.io
From 0.0.0-0 · fixed in 0.33.0
- gix-worktreecrates.io
From 0.0.0-0 · fixed in 0.34.0
- gix-worktree-statecrates.io
fixed in 0.11.0
- gitoxidecrates.io
fixed in 0.36.0
- gix-fscrates.io
fixed in 0.11.0
- gix-worktreecrates.io
fixed in 0.34.0
- gixcrates.io
fixed in 0.63.0
- gitoxide-corecrates.io
fixed in 0.38.0
- gix-indexcrates.io
fixed in 0.33.0