Cyber Resilience

CVE-2024-43615

Path Traversal in Microsoft Windows 10 1809 ≤ 10.0.17763.6414

Published
08 October 2024
Modified
21 October 2024
Patch / advisory
CVSS Score v3.1 7.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.012 65th percentile
Risk Priority 61 floored blend · peak EPSS

Summary

CVE-2024-43615 is a high-severity External Control of File Name or Path (CWE-73) vulnerability in Microsoft Windows 10 1809. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked in the top 35% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Microsoft OpenSSH for Windows contains a remote code execution vulnerability tracked as CVE-2024-43615. The flaw is present in the OpenSSH implementation shipped with Windows and carries a CVSS 3.1 score of 7.1, reflecting network attack vectors that require low privileges, user interaction, and high attack complexity to reach high impact on confidentiality, integrity, and availability. The associated weakness is categorized under CWE-73.

An authenticated attacker who can reach an affected Windows system over the network may leverage the vulnerability to execute arbitrary code on the target. Successful exploitation depends on the victim performing specific actions and on conditions that increase attack complexity, ultimately allowing the attacker to compromise the confidentiality, integrity, and availability of the system.

The official Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43615 supplies remediation guidance and patch information for the affected OpenSSH component. The EPSS score has remained flat at 0.0892 since disclosure, indicating no material increase in observed exploitation interest.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Microsoft OpenSSH for Windows Remote Code Execution Vulnerability

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1574.007 Path Interception by PATH Environment Variable Stealth
Adversaries may execute their own malicious payloads by hijacking environment variables used to load libraries.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-43581Same product: Microsoft Windows 10 1809
CVE-2025-59511Same product: Microsoft Windows 10 1809
CVE-2025-49760Same product: Microsoft Windows 10 1809
CVE-2026-24287Same product: Microsoft Windows 10 1809
CVE-2025-24996Same product: Microsoft Windows 10 1809
CVE-2025-59185Same product: Microsoft Windows 10 1809
CVE-2025-21377Same product: Microsoft Windows 10 1809
CVE-2025-33053Same product: Microsoft Windows 10 1809
CVE-2024-43451Same product: Microsoft Windows 10 1809
CVE-2025-24054Same product: Microsoft Windows 10 1809

Affected Assets

microsoft
windows 10 1809
≤ 10.0.17763.6414
microsoft
windows 10 21h2
≤ 10.0.19044.5011
microsoft
windows 10 22h2
≤ 10.0.19045.5011
microsoft
windows 11 21h2
≤ 10.0.22000.3260
microsoft
windows 11 22h2
≤ 10.0.22621.4317
microsoft
windows 11 23h2
≤ 10.0.22631.4317
microsoft
windows 11 24h2
≤ 10.0.26100.2033
microsoft
windows server 2019
≤ 10.0.17763.6414
microsoft
windows server 2022
≤ 10.0.20348.2762
microsoft
windows server 2022 23h2
≤ 10.0.25398.1189

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly rejects or sanitizes untrusted path strings before they reach filesystem operations.

Enforces authorization checks on the actual resource accessed, blocking unauthorized files even when a malicious path is supplied.

Least-privilege limits the set of files or directories any subject can affect, shrinking the blast radius of a path-control flaw.

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 full match
prevents

Secure SDLC practices include input validation and path sanitization that eliminate this weakness.

PR.AA-05 mostly match
prevents

Least-privilege file authorization directly limits damage from externally controlled paths.

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.

finds

Security testing can detect path-traversal issues but does not itself implement preventive controls.

prevents

Secure development lifecycle mandates input validation and path-handling controls that directly prevent external file/path manipulation.

prevents

Application security requirements explicitly call for controls against untrusted input influencing file operations.

prevents

Secure architecture principles discourage unsafe path construction but do not prescribe concrete file-name controls.

prevents

Secure coding standards require canonicalization, allow-listing, and bounds checks on file paths, directly eliminating CWE-73.

mitigates

Information access restriction limits which files can be reached, indirectly reducing impact of path manipulation.

References