CVE-2024-35197

GHSA-49jc-r788-3fc9 · RUSTSEC-2024-0351 · RUSTSEC-2024-0352 · RUSTSEC-2024-0353 · published 22 May 2024 · updated 9 Nov 2026

gix refs and paths with reserved Windows device names access the devices

5.4MediumCVSS 5.4EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in gix-index 0.33.0, gix-ref 0.44.0 and gix-worktree 0.34.0.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Byron<0.36.0
cargo: gix-index>=0.0.0-0 <0.33.00.33.0
cargo: gix-ref>=0.0.0-0 <0.44.00.44.0
cargo: gix-worktree>=0.0.0-0 <0.34.00.34.0

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in gix-index (Cargo), strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2024-35197 severity on Zeptric[![CVE-2024-35197](https://zeptric.io/badge/cve/CVE-2024-35197.svg)](https://zeptric.io/cve/CVE-2024-35197)