Security Resilience

CVE-2023-35390

Command Injection in Microsoft Visual Studio 2022 17.2.0 – 17.2.18

Published
08 August 2023
Modified
10 August 2026
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.021 81th percentile
Risk Priority 61 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-35390 is a high-severity Command Injection (CWE-77) vulnerability in Microsoft Visual Studio 2022. Its CVSS base score is 7.8 (High).

Operationally, ranked in the top 19% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

.NET and Visual Studio Remote Code Execution Vulnerability

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-33127Same product: Microsoft .Net
CVE-2023-33135Same product: Microsoft .Net
CVE-2023-32032Same product: Microsoft .Net
CVE-2023-33126Same product: Microsoft .Net
CVE-2023-33128Same product: Microsoft .Net
CVE-2025-62214Same product: Microsoft Visual Studio 2022
CVE-2023-28260Same product: Microsoft .Net
CVE-2025-47959Same product: Microsoft Visual Studio 2022
CVE-2025-32702Same product: Microsoft Visual Studio 2022
CVE-2025-53773Same product: Microsoft Visual Studio 2022

Affected Assets

microsoft
.net
6.0.0 — 6.0.21 · 7.0.0 — 7.0.10
microsoft
visual studio 2022
17.2.0 — 17.2.18 · 17.4.0 — 17.4.10 · 17.6.0 — 17.6.6

Mitigating Controls

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.

blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reduce command injection defects, but leaves a minority slice (e.g. incomplete implementation of those practices, outsourced development without full assurance, or post-SDLC changes) where the weakness can still arise and be exploitable.

blocks

Application security requirements explicitly call for controls against injection flaws including command injection.

blocks

A.8.27 mandates security-by-design principles (e.g. distrust external input, secure session control, data validation/sanitization, least privilege) and design reviews that can stop command injection from being introduced, but this is only a minority slice of CWE-77 because the weakness can still arise in code that bypasses those principles, in non-reviewed components, or in runtime injection vectors the architecture review does not reach.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing in development catches command-injection vulnerabilities before release.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-77, a class-level weakness, and none of its children carries one either.

References