cve.bz

CVE-2024-35186 byron gitoxide: Relative Path Traversal

8.8 highEPSS 0.8%Fix available

High (8.8) in byron gitoxide. EPSS 0.8% 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. During checkout, `gix-worktree-state` does not verify that paths point to locations in the working tree. A specially crafted repository can, when cloned, place new files anywhere writable by the application. This vulnerability leads to a major loss of confidentiality, integrity, and availability, but creating files outside a working tree without attempting to execute code can directly impact integrity as well. This vulnerability has been patched in version(s) 0.36.0.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 58th 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: total, 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-23 Relative Path Traversal
OWASP Top 10
A01:2025 Broken Access Control
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-fs (crates.io): fixed in 0.11.0
  • gix-worktree (crates.io): fixed in 0.34.0
  • gix (crates.io): fixed in 0.63.0
  • gitoxide-core (crates.io): fixed in 0.38.0
  • gix-index (crates.io): fixed in 0.33.0
  • Debian, openSUSE: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2024-35186 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-35186?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-35186?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-35186 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-7w47-3wg8-547ccrates.iogix-worktree-state<0.11.00.11.0
GHSA-7w47-3wg8-547ccrates.iogitoxide<0.36.00.36.0
GHSA-7w47-3wg8-547ccrates.iogix-fs<0.11.00.11.0
GHSA-7w47-3wg8-547ccrates.iogix-worktree<0.34.00.34.0
GHSA-7w47-3wg8-547ccrates.iogix<0.63.00.63.0
GHSA-7w47-3wg8-547ccrates.iogitoxide-core<0.38.00.38.0
GHSA-7w47-3wg8-547ccrates.iogix-index<0.33.00.33.0
RUSTSEC-2024-0348crates.iogix-index>=0.0.0-0 <0.33.00.33.0
RUSTSEC-2024-0349crates.iogix-worktree>=0.0.0-0 <0.34.00.34.0
RUSTSEC-2024-0350crates.iogix-fs>=0.0.0-0 <0.11.00.11.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13, 14rust-gix-fs0.11.3-1DEBIAN-CVE-2024-35186
Debian13, 14rust-gix-index0.33.1-1DEBIAN-CVE-2024-35186
Debian13, 14rust-gix-worktree0.34.1-1DEBIAN-CVE-2024-35186
Ubuntu24.04:LTSrust-gix-fsno fix listedUBUNTU-CVE-2024-35186
openSUSETumbleweedgitoxide0.36.0-1.1openSUSE-SU-2024:13987-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-139 Relative Path Traversal Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON