Security Resilience

CVE-2023-24884

Microsoft Windows Server 2012 r2

Published
11 April 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.016 76th percentile
Risk Priority 68 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-24884 is a high-severity Incorrect Conversion between Numeric Types (CWE-681) vulnerability in Microsoft Windows Server 2012. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 24% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

Microsoft PostScript and PCL6 Class Printer Driver Remote Code Execution Vulnerability

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
T1003.004 LSA Secrets Credential Access
Adversaries with SYSTEM access to a host may attempt to access Local Security Authority (LSA) secrets, which can contain a variety of different credential materials, such as credentials for service accounts.
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
T1008 Fallback Channels Command And Control
Adversaries may use fallback or alternate communication channels if the primary channel is compromised or inaccessible in order to maintain reliable command and control and to avoid data transfer thresholds.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-23401Same product: Microsoft Windows 10 1507
CVE-2023-23388Same product: Microsoft Windows 10 1507
CVE-2023-29346Same product: Microsoft Windows 10 1507
CVE-2024-26162Same product: Microsoft Windows 10 1507
CVE-2023-28243Same product: Microsoft Windows 10 1507
CVE-2023-24864Same product: Microsoft Windows 10 1507
CVE-2023-24929Same product: Microsoft Windows 10 1507
CVE-2023-24927Same product: Microsoft Windows 10 1507
CVE-2023-24885Same product: Microsoft Windows 10 1507
CVE-2023-24925Same product: Microsoft Windows 10 1507

Affected Assets

microsoft
windows 10 1507
≤ 10.0.10240.19869
microsoft
windows 10 1607
≤ 10.0.14393.5850
microsoft
windows 10 1809
≤ 10.0.17763.4252
microsoft
windows 10 20h2
≤ 10.0.19042.2846
microsoft
windows 10 21h2
≤ 10.0.19044.2846
microsoft
windows 10 22h2
≤ 10.0.19045.2846
microsoft
windows 11 21h2
≤ 10.0.22000.1817
microsoft
windows 11 22h2
≤ 10.0.22621.1555
microsoft
windows server 2012
all versions, r2
microsoft
windows server 2016
all versions
+2 more product configuration(s) — see NVD for full list

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 partial match
blocks

Secure SDLC practices directly require code reviews, static analysis, and developer training that catch and prevent numeric type-conversion errors.

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

Secure development lifecycle includes type-safety and conversion checks that reduce numeric truncation risks.

blocks

A.8.26 requires identifying and specifying security requirements (including resilience against certain attacks like buffer overflows or SQL injection) but does not itself implement any conversion checks, bounds validation, or other mechanisms that would stop exploitation of incorrect numeric type conversions

blocks

Secure architecture principles promote strong typing and safe conversion practices.

prevents

Secure coding standards directly address correct numeric type conversions and overflow checks.

finds

Security testing can detect numeric conversion defects before release.

References