cve.bz

CVE-2024-35197 byron gitoxide

5.4 mediumEPSS 0.4%Fix available

Medium (5.4) in byron gitoxide. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in gix-worktree-state 0.11.0.

On this page
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.

Severity

CVSS 3.1

5.4 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2024-05-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-67 Improper Handling of Windows Device Names
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • gix-worktree-state (crates.io): fixed in 0.11.0
  • gitoxide (crates.io): fixed in 0.36.0
  • gix-worktree (crates.io): fixed in 0.34.0
  • gitoxide-core (crates.io): fixed in 0.38.0
  • gix (crates.io): fixed in 0.63.0
  • gix-ref (crates.io): fixed in 0.44.0
  • gix-index (crates.io): fixed in 0.33.0

Ask an AI about this CVE

Show the promptExplain CVE-2024-35197 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-35197?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-35197?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-35197 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Byron gitoxide< 0.36.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-49jc-r788-3fc9crates.iogix-worktree-state<0.11.00.11.0
GHSA-49jc-r788-3fc9crates.iogitoxide<0.36.00.36.0
GHSA-49jc-r788-3fc9crates.iogix-worktree<0.34.00.34.0
GHSA-49jc-r788-3fc9crates.iogitoxide-core<0.38.00.38.0
GHSA-49jc-r788-3fc9crates.iogix<0.63.00.63.0
GHSA-49jc-r788-3fc9crates.iogix-ref<0.44.00.44.0
GHSA-49jc-r788-3fc9crates.iogix-index<0.33.00.33.0
RUSTSEC-2024-0351crates.iogix-ref>=0.0.0-0 <0.44.00.44.0
RUSTSEC-2024-0352crates.iogix-index>=0.0.0-0 <0.33.00.33.0
RUSTSEC-2024-0353crates.iogix-worktree>=0.0.0-0 <0.34.00.34.0

References

Check your stackJSON