gix refs and paths with reserved Windows device names access the devices
Byron gitoxide
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| gix-worktree-state crates.io |
|
|
| gitoxide crates.io |
|
|
| gix-worktree crates.io |
Byron gitoxide
| Product | Affected | Fixed in |
|---|---|---|
| gix-worktree-state crates.io |
|
|
| gitoxide crates.io |
|
|
| gix-worktree crates.io |
< 0.34.0≥ 0.0.0-0 · < 0.34.0
|
| gitoxide-core crates.io |
|
|
| gix crates.io |
|
|
| gix-ref crates.io |
|
|
| gix-index crates.io |
|
|
gitoxide is a pure Rust implementation of Git. On Windows, fetching refs that clash with legacy device names reads from the devices, and checking out paths that clash with such names writes arbitrary data to the devices. This allows a repository, when cloned, to cause indefinite blocking or the production of arbitrary message that appear to have come from the application, and potentially other harmful effects under limited circumstances. If Windows is not used, or untrusted repositories are not cloned or otherwise used, then there is no impact. A minor degradation in availability may also be possible, such as with a very large file named `CON`, though the user could interrupt the application.
From the CVE record · GitHub_M
On Windows, gitoxide can read from devices when fetching refs whose names clash with legacy device names, or write arbitrary data to devices when checking out paths with such names. Cloning or otherwise using an untrusted repository can cause indefinite blocking or messages that appear to come from the application; other harmful effects may be possible under limited circumstances. There is no impact without Windows or without use of untrusted repositories.
Engineers using Byron gitoxide on Windows should check for gix-worktree-state <0.11.0, gitoxide <0.36.0, gix-worktree <0.34.0, gitoxide-core <0.38.0, gix <0.63.0, gix-ref <0.44.0, or gix-index <0.33.0.