Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-21323 is a high-severity Absolute Path Traversal (CWE-36) vulnerability in Microsoft Defender For Iot. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 12% 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 Defender for IoT contains a remote code execution vulnerability identified as CVE-2024-21323. The flaw carries a CVSS 3.1 score of 8.8 and is associated with CWE-36. It affects the Defender for IoT product and permits an attacker to execute arbitrary code on affected systems.
An authenticated attacker with low privileges can exploit the issue over the network with low attack complexity and no user interaction required. Successful exploitation grants full control over confidentiality, integrity, and availability on the target, enabling remote code execution within the impacted environment.
The official Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21323 provides patch and mitigation guidance for the vulnerability. The associated EPSS score has remained flat at 0.1027 since disclosure with no observed upward trajectory.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-19035
Vulnerability Data
Microsoft Defender for IoT Remote Code Execution Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly stops construction of absolute paths from untrusted data before they reach file operations.
Enforced access authorizations can limit which resources are reachable even if a traversal succeeds.
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.
Secure SDLC practices directly require input validation and path sanitization that prevent absolute path traversal.
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.25 mandates secure SDLC practices (secure requirements, checkpoints, secure coding guidelines, testing including code scans/penetration tests) that reach many path-traversal instances in custom software, but leaves a bounded remainder (e.g. third-party components, misconfigured outsourced development, or incomplete enforcement of guidelines) where the weakness can still be introduced and exploited.
Application security requirements typically mandate controls against path traversal in file-access functions.
A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust-external-input, hardening, design review against attack patterns) that reach a minority slice of absolute path traversal (e.g. explicit path canonicalization rules or sandboxing), but most instances arise from ordinary string-concatenation flaws in custom code that the clause's high-level engineering principles do not themselves stop from being written or exploited.
Secure coding standards directly require neutralization of absolute path sequences in pathname construction.
Security testing in development can detect absolute path traversal via static analysis and fuzzing.