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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-35197: 0.45% estimated exploitation activity in the next 30 days; percentile 39.03 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details It is possible to create a Git repository that contains references or filenames that Windows treats as legacy DOS-style aliases for system devices. When such a repository is cloned: - In references, gix-ref does not include a check for such names before attempting to access them on disk, which reads from the devices, though the ability to exfiltrate data appears limited. - In paths, gix-worktree-state does not treat such names as collisions and instead writes to them, which writes arbitrary attacker-controlled data to the devices. Some such device names refer to devices that are…

Published by the source

22 May 2024, 14:13 UTC

Last modified by the source

5 Aug 2024, 05:04 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-49jc-r788-3fc9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-35197

Advisory: gix refs and paths with reserved Windows device names access the devices
IDs: CVE-2024-35197, GHSA-49jc-r788-3fc9
Record: https://patchnext.com/advisories/cve-2024-35197 (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gix 0.63.0; gix-index 0.33.0; gitoxide 0.36.0; gitoxide-core 0.38.0; gix-worktree 0.34.0; gix-worktree-state 0.11.0; gix-ref 0.44.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io gix: affected < 0.63.0; fixed in 0.63.0
- crates.io gix-index: affected < 0.33.0; fixed in 0.33.0
- crates.io gitoxide: affected < 0.36.0; fixed in 0.36.0
- crates.io gitoxide-core: affected < 0.38.0; fixed in 0.38.0
- crates.io gix-worktree: affected < 0.34.0; fixed in 0.34.0
- crates.io gix-worktree-state: affected < 0.11.0; fixed in 0.11.0
- crates.io gix-ref: affected < 0.44.0; fixed in 0.44.0

## Suggested inspection (read-only)
- crates.io gix: check the installed version with your package manager.
- crates.io gix-index: check the installed version with your package manager.
- crates.io gitoxide: check the installed version with your package manager.
- crates.io gitoxide-core: check the installed version with your package manager.
- crates.io gix-worktree: check the installed version with your package manager.
- crates.io gix-worktree-state: check the installed version with your package manager.
- crates.io gix-ref: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gix, gix-index, gitoxide, gitoxide-core, gix-worktree, gix-worktree-state, gix-ref.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-49jc-r788-3fc9 (GitHub-reviewed advisory GHSA-49jc-r788-3fc9 lists affected ranges: crates.io gix-worktree-state >=0 =0 =0 =0 =0 =0 =0 <0.33.0)

Commands are suggestions: review each one before running it.