Cyber Resilience

CVE-2023-23379

Path Traversal in Microsoft Defender For Iot ≤ 22.3.6

Path Traversal
Published
14 February 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0044 37th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2023-23379 is a high-severity Relative Path Traversal (CWE-23) vulnerability in Microsoft Defender For Iot. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

Microsoft Defender for IoT Elevation of Privilege Vulnerability

CWE(s)
CWE-23NVD-CWE-noinfo

Related Threats

MITRE ATT&CK Enterprise Techniques

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.
attack.mitre.org →
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.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-29053Same product: Microsoft Defender For Iot
CVE-2024-21323Same product: Microsoft Defender For Iot
CVE-2024-21322Same product: Microsoft Defender For Iot
CVE-2024-29054Same product: Microsoft Defender For Iot
CVE-2024-29055Same product: Microsoft Defender For Iot
CVE-2026-56196Same vendor: Microsoft
CVE-2023-35359Same vendor: Microsoft
CVE-2025-62552Same vendor: Microsoft
CVE-2024-30010Same vendor: Microsoft
CVE-2024-43614Same vendor: Microsoft

Affected Assets

microsoft
defender for iot
≤ 22.3.6

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 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 path sanitization that prevent relative 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.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches path traversal via static/dynamic analysis, but does not itself implement the fix.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and path-handling controls that directly prevent relative path traversal.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against path traversal and other injection flaws.

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

Secure architecture principles include directory isolation and canonicalization, reducing but not eliminating traversal risk.

A.8.28 Secure coding partial match
prevents

Secure coding standards require neutralizing path traversal sequences, directly addressing CWE-23.

A.8.3 Information access restriction partial match
mitigates

Information access restriction limits which files can be reached, mitigating impact but not preventing the traversal flaw.

References