CVE-2024-35197Public exploitNetwork attack vector

Output spoofing and hangs via Windows device names

Published May 23, 2024 · Updated Aug 2, 2024

Improper Windows device-name handling in GitoxideLabs gitoxide before 0.36.0 allows remote attackers to interrupt or spoof gix output. During clone, gix-ref opens attacker-named refs such as CON as devices, while gix-worktree-state treats matching paths as ordinary files and writes attacker-controlled bytes to them. The flaw is reachable only on Windows when an untrusted repository is cloned or otherwise used; it can block on console input, print deceptive text, or interfere with available devices.

CVSS severity5.4
Medium
EPSS probability0.45%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper Windows device-name handling in GitoxideLabs gitoxide before 0.36.0 allows remote attackers to interrupt or spoof gix output. During clone, gix-ref opens attacker-named refs such as CON as devices, while gix-worktree-state treats matching paths as ordinary files and writes attacker-controlled bytes to them. The flaw is reachable only on Windows when an untrusted repository is cloned or otherwise used; it can block on console input, print deceptive text, or interfere with available devices.

The record

CVE
CVE-2024-35197
Published
May 23, 2024
Updated
Aug 2, 2024
Vendor
GitoxideLabs
Product
gitoxide
Classifications
CWE-67, T1204.002
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 23, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <0.36.0
  2. Affected versionversion=< 0.36.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

GitoxideLabs · gitoxideversion=0 <0.36.0; version=< 0.36.0

Published CVSS scores

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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-67Improper Handling of Windows Device Names
T1204.002Malicious File

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo