Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.44% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: gitoxide (crates.io) 0.36.0; gitoxide-core (crates.io) 0.38.0; gix (crates.io) 0.63.0.

Low priority for now. Upgrade to gitoxide (crates.io) 0.36.0; gitoxide-core (crates.io) 0.38.0; gix (crates.io) 0.63.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.4 · v3.1—No exploit Fix available
Published
May 23, 2024
Updated
Jun 17, 2026
EPSS
0.4% · 39th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
5.4
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-35197

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for byron records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
byrongitoxide

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • Byron gitoxide

    • < 0.36.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
crates.iogitoxidebefore 0.36.00.36.0
crates.iogitoxide-corebefore 0.38.00.38.0
crates.iogixbefore 0.63.00.63.0
crates.iogix-indexfrom 0.0.0-0 · before 0.33.00.33.0
crates.iogix-indexbefore 0.33.00.33.0
crates.iogix-reffrom 0.0.0-0 · before 0.44.00.44.0
crates.iogix-refbefore 0.44.00.44.0
crates.iogix-worktreefrom 0.0.0-0 · before 0.34.00.34.0
crates.iogix-worktreebefore 0.34.00.34.0
crates.iogix-worktree-statebefore 0.11.00.11.0

Same product

byron: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-35186gix traversal outside working tree enables arbitrary code execution
    35Monitor
  • CVE-2024-40644gitoxide's gix-path can use a fake program files location
    27Monitor
  • CVE-2024-32884gix-transport indirect code execution via malicious username
    25Monitor

Published before and after this one in the same product

  • Later →CVE-2024-43785Aug 22, 2024 · gitoxide-core does not neutralize special characters for terminals
    10Monitor
  • Later →CVE-2024-45305Sep 2, 2024 · gix-path uses local config across repos when it is the highest scope
    10Monitor
  • Later →CVE-2024-45405Sep 6, 2024 · gix-path improperly resolves configuration path reported by Git
    24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
crates.io:gitoxide0.36.0Package registry (OSV)
crates.io:gitoxide-core0.38.0Package registry (OSV)
crates.io:gix0.63.0Package registry (OSV)
crates.io:gix-index0.33.0Package registry (OSV)
crates.io:gix-ref0.44.0Package registry (OSV)
crates.io:gix-worktree0.34.0Package registry (OSV)
crates.io:gix-worktree-state0.11.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
Low

Weakness class (CWE)

CWE-67 · Improper Handling of Windows Device Names

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records