gix traversal outside working tree enables arbitrary code execution
Byron gitoxide
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| gix-worktree-state crates.io |
|
|
| gitoxide crates.io |
|
|
| gix-fs crates.io |
Byron gitoxide
| Product | Affected | Fixed in |
|---|---|---|
| gix-worktree-state crates.io |
|
|
| gitoxide crates.io |
|
|
| gix-fs crates.io |
< 0.11.0≥ 0.0.0-0 · < 0.11.0
|
| gix-worktree crates.io |
|
|
| gix crates.io |
|
|
| gitoxide-core crates.io |
|
|
| gix-index crates.io |
|
|
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.
From the CVE record · GitHub_M
During checkout, gix-worktree-state does not verify that paths stay within the working tree. If a user clones a specially crafted repository, it can create files anywhere the application has write access.
Check applications using gitoxide before 0.36.0, gix-worktree-state or gix-fs before 0.11.0, gix-worktree before 0.34.0, gix before 0.63.0, gitoxide-core before 0.38.0, or gix-index before 0.33.0.