gitoxide before 0.33.0 Path Traversal via symlink following
GitoxideLabs gitoxide
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| GitoxideLabs gitoxide |
|
|
| GitoxideLabs gitoxide |
|
|
| GitoxideLabs gitoxide |
|
|
GitoxideLabs gitoxide
| Product | Affected | Fixed in |
|---|---|---|
| GitoxideLabs gitoxide |
|
|
| GitoxideLabs gitoxide |
|
|
| GitoxideLabs gitoxide |
|
|
| GitoxideLabs gitoxide |
|
|
gix-worktree-state before 0.33.0 (part of gitoxide) allows writing files outside the worktree on Windows. gix_worktree_state::checkout() follows an existing terminal symlink during non-exclusive (incremental) materialization (destination_is_initially_empty: false) when core.symlinks is true. If a symlink entry (mode 120000) is first checked out at a path P pointing outside the worktree, a subsequent incremental checkout of a regular-file entry (mode 100644) at the same path follows the existing reparse point and writes the blob content through the link, overwriting files outside the worktree.
From the CVE record · VulnCheck
On Windows, gix-worktree-state before 0.33.0 can write outside the worktree during a non-exclusive incremental checkout when core.symlinks is true. If a symlink pointing outside the worktree is checked out at a path and a regular file is later checked out at the same path, checkout follows the existing link and overwrites the external file.
Engineers using gitoxide with gix-worktree-state versions before 0.33.0 on Windows should check their deployments.