Cyber Resilience

CVE-2023-21805

Command Injection in Microsoft Windows Server 2008 r2

Published
14 February 2023
Modified
21 November 2024
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.0074 51th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2023-21805 is a high-severity Command Injection (CWE-77) vulnerability in Microsoft Windows Server 2008. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 49% 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

Windows MSHTML Platform Remote Code Execution Vulnerability

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
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.
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
T1059.008 Network Device CLI Execution
Adversaries may abuse scripting or built-in command line interpreters (CLI) on network devices to execute malicious command and payloads.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-36805Same product: Microsoft Windows 10 1607
CVE-2025-54100Same product: Microsoft Windows 10 1607
CVE-2026-49179Same product: Microsoft Windows 10 1607
CVE-2026-32183Same product: Microsoft Windows 10 1607
CVE-2026-58635Same product: Microsoft Windows 10 1809
CVE-2019-0541Same product: Microsoft Windows 10 1607
CVE-2023-21802Same product: Microsoft Windows 10
CVE-2023-21694Same product: Microsoft Windows 10
CVE-2023-23421Same product: Microsoft Windows 10
CVE-2023-21812Same product: Microsoft Windows 10

Affected Assets

microsoft
windows 10
≤ 10.0.10240.19747
microsoft
windows 10 1607
≤ 10.0.14393.5717
microsoft
windows 10 1809
≤ 10.0.17763.4010
microsoft
windows 10 20h2
≤ 10.0.19042.2604
microsoft
windows 10 21h2
≤ 10.0.19044.2604
microsoft
windows 10 22h2
≤ 10.0.19045.2604
microsoft
windows 11 21h2
≤ 10.0.22000.1574
microsoft
windows 11 22h2
≤ 10.0.22621.1265
microsoft
windows server 2008
all versions, r2
microsoft
windows server 2012
all versions, r2
+3 more product configuration(s) — see NVD for full list

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)
  • V1.2.3
  • V1.2.5
  • V1.2.8
  • V1.2.9

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 neutralization that prevent command injection.

DE.CM-09 partial match
prevents

Runtime monitoring of software and data can detect anomalous command execution resulting from injection.

ID.RA-01 partial match
prevents

Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.

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.

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.

prevents

Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.

prevents

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

prevents

Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.

none

Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.

References