# Refs and paths with reserved Windows device names access the devices

Advisory record · `GHSA-49jc-r788-3fc9`

- **Identifiers:** `GHSA-49jc-r788-3fc9` · `CVE-2024-35197` · `RUSTSEC-2024-0351` · `RUSTSEC-2024-0352` · `RUSTSEC-2024-0353`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-67](https://cwe.mitre.org/data/definitions/67.html)
- **Tags:** [CWE-67](https://agentprime.io/advisories/tag/cwe-67.md)
- **Published:** 22 May 2024
- **Updated:** 12 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 May 2024, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `gix-ref` (crates.io): affected `>=0.0.0-0, <0.44.0`; fixed in `0.44.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> gix-ref before 0.44.0 on Windows accesses devices when refs or paths use legacy device names such as CON or COM1. A malicious repository cloned on Windows can cause a hang while waiting for console input, or print attacker-chosen text that looks like application output. Upgrade to gix-ref 0.44.0 or later.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0045, the 39th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:24 UTC: First seen by agentprime
- 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/RUSTSEC-2024-0351)

## Sources

- [GitHub Advisory Database: GHSA-49jc-r788-3fc9](https://github.com/advisories/GHSA-49jc-r788-3fc9)
- [OSV: GHSA-49jc-r788-3fc9](https://osv.dev/vulnerability/GHSA-49jc-r788-3fc9)
- <https://crates.io/crates/gix-ref>
- <https://rustsec.org/advisories/RUSTSEC-2024-0351.html>
- <https://github.com/GitoxideLabs/gitoxide/commit/79dce79c62f6072aa2653780d590dc3993dfa401>
- <https://github.com/advisories/GHSA-49jc-r788-3fc9>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-35197>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-49jc-r788-3fc9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-49jc-r788-3fc9/>. Everything for agents: <https://agentprime.io/llms.txt>.