Cyber Resilience

CVE-2023-21815

Memory Safety in Microsoft Visual Studio 2022 17.0 – 17.0.19

Memory Safety
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.0052 42th percentile
Risk Priority 60 floored blend · peak EPSS

Summary

CVE-2023-21815 is a high-severity Wrap or Wraparound (CWE-191) vulnerability in Microsoft Visual Studio 2022. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

Visual Studio Remote Code Execution Vulnerability

CWE(s)
CWE-191NVD-CWE-noinfo

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
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 →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-23381Same product: Microsoft Visual Studio 2017
CVE-2023-28296Same product: Microsoft Visual Studio 2017
CVE-2024-28933Same product: Microsoft Visual Studio 2019
CVE-2024-28930Same product: Microsoft Visual Studio 2019
CVE-2023-36794Same product: Microsoft Visual Studio 2017
CVE-2023-36796Same product: Microsoft Visual Studio 2017
CVE-2023-33139Same product: Microsoft Visual Studio 2017
CVE-2023-28263Same product: Microsoft Visual Studio 2019
CVE-2023-28262Same product: Microsoft Visual Studio 2019
CVE-2023-36759Same product: Microsoft Visual Studio 2019

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

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 directly prevent integer underflow defects via input validation, bounds checking, and static analysis.

ID.RA-01 partial match
prevents

Vulnerability scanning and code analysis can surface underflow flaws after they are introduced.

PR.PS-02 partial match
prevents

Routine patching can remediate known underflow bugs once they are discovered in deployed software.

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 integer underflow defects before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and arithmetic checks that prevent integer underflow.

A.8.26 Application security requirements partial match
prevents

Application security requirements include bounds checking and safe arithmetic to avoid underflow conditions.

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

Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prescribe safe integer handling and overflow/underflow prevention.

References