CVE-2024-35197 | gix refs and paths with reserved Windows device names access the devices

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.

Published: 2024-05-23 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-35197 is rated Low Risk (34.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.45%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-35197

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.06% 0.45% +0.39%
2 2026-06-11 0.04% 0.06% +0.01%
3 2025-11-21 — 0.04% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-35197

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.4 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.8 2.5 [email protected]

Weakness enumeration for CVE-2024-35197

GitHub Security Advisory for CVE-2024-35197

GHSA-49jc-r788-3fc9 · Severity: medium · Ecosystem: rust — gix refs and paths with reserved Windows device names access the devices

OS Trackers for CVE-2024-35197

vendor priority summary link
debian unimportant CVE-2024-35197 unimportant priority: Debian including 3 source packages (rust-gix-index, rust-gix-ref, rust-gix-worktree), 9 status rows across 3 suites (forky, sid, trixie): resolved 9. https://security-tracker.debian.org/tracker/CVE-2024-35197
suse medium — https://www.suse.com/security/cve/CVE-2024-35197/

Affected software / configurations for CVE-2024-35197

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2024-35197

cvelogic Threat Intelligence