Cyber Resilience

CVE-2024-35197

Published
23 May 2024
Modified
15 April 2026
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
EPSS Score 0.0045 37th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2024-35197 is a medium-severity Improper Handling of Windows Device Names (CWE-67) vulnerability. Its CVSS base score is 5.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-67

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-21860Shared CWE-67
CVE-2025-66221Shared CWE-67
CVE-2026-27199Shared CWE-67
CVE-2024-51745Shared CWE-67

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation directly stops construction of pathnames containing Windows device names from untrusted data.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles include safe pathname construction and device-name filtering.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and safe pathname handling that prevent device-name misuse.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect and prevent device-name pathname vulnerabilities.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle requires input validation and path handling rules that would prevent device-name misuse.

A.8.26 Application security requirements partial match
prevents

Application security requirements include validation of file/path inputs, mitigating device-name attacks.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles mandate safe pathname construction and canonicalization.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address proper handling of Windows reserved device names in pathnames.

References