Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-24872 is a high-severity Out-of-bounds Read (CWE-125) vulnerability in Microsoft Windows Server 2012. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 32% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Microsoft PostScript and PCL6 Class Printer Driver is affected by a remote code execution vulnerability tracked as CVE-2023-24872. The flaw carries a CVSS 3.1 score of 8.8 and is associated with out-of-bounds read behavior (CWE-125). It was disclosed on 14 March 2023 and impacts the affected printer driver components when processing certain print jobs over the network.
An attacker with low privileges and network access can exploit the issue without user interaction, resulting in full compromise of confidentiality, integrity, and availability on the target system. The attack vector is rated as network-reachable with low complexity and unchanged scope, allowing remote code execution in the context of the driver process.
Microsoft security advisories at the referenced update guide URL describe the availability of patches that address the vulnerability; administrators are directed to apply the updates through standard Windows update channels. The EPSS score remains flat at 0.1122 with no material increase after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-28862
Vulnerability Data
Microsoft PostScript and PCL6 Class Printer Driver Remote Code Execution Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
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.
Secure-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.
Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.
Routine patching replaces vulnerable code containing out-of-bounds read flaws.
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.
Security testing in development and acceptance includes fuzzing and static analysis that detect out-of-bounds read defects before release.
Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.
Secure development life cycle mandates input validation and bounds checking that directly prevent out-of-bounds reads.
Application security requirements include explicit bounds and memory-safety specifications that mitigate buffer over-reads.
Secure system architecture and engineering principles require memory-safe design patterns and runtime protections against out-of-bounds access.
Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.