Cyber Resilience

CVE-2023-21566

Path Traversal in Microsoft Visual Studio 2022 17.0 – 17.0.19

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.0037 30th percentile
Risk Priority 62 floored blend · peak EPSS

Summary

CVE-2023-21566 is a high-severity External Control of File Name or Path (CWE-73) vulnerability in Microsoft Visual Studio 2022. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

Visual Studio Elevation of Privilege Vulnerability

CWE(s)
CWE-73NVD-CWE-noinfo

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.
attack.mitre.org →
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.
attack.mitre.org →
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 →
T1574.007 Path Interception by PATH Environment Variable Stealth
Adversaries may execute their own malicious payloads by hijacking environment variables used to load libraries.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-21815Same product: Microsoft Visual Studio 2017
CVE-2023-23381Same product: Microsoft Visual Studio 2017
CVE-2023-28296Same product: Microsoft Visual Studio 2017
CVE-2024-29060Same product: Microsoft Visual Studio 2017
CVE-2024-20652Same vendor: Microsoft
CVE-2026-21249Same vendor: Microsoft
CVE-2026-20925Same vendor: Microsoft
CVE-2025-47956Same vendor: Microsoft
CVE-2025-24996Same vendor: Microsoft
CVE-2026-20931Same vendor: Microsoft

Affected Assets

microsoft
visual studio 2017
15.0 — 15.9.52
microsoft
visual studio 2019
16.0 — 16.11.24
microsoft
visual studio 2022
17.0 — 17.0.19 · 17.2 — 17.2.13 · 17.4 — 17.4.5

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

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

SI-10 Information Input Validation
addresses: CWE-73

Rejects externally supplied file or resource identifiers that fail validity checks.

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.

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

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

A.8.25 Secure development life cycle partial match
prevents

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

A.8.26 Application security requirements partial match
prevents

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

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

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

A.8.28 Secure coding partial match
prevents

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

A.8.3 Information access restriction partial match
mitigates

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

References