Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2023-24883 is a medium-severity Buffer Over-read (CWE-126) vulnerability in Microsoft Windows Server 2012. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked in the top 29% 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.
CVE-2023-24883 is an information disclosure vulnerability in the Microsoft PostScript and PCL6 Class Printer Driver, carrying a CVSS 3.1 base score of 6.5. The flaw is associated with CWE-126 and permits unauthorized exposure of sensitive data when the affected driver components process certain inputs.
An attacker with low privileges can exploit the issue over a network connection without user interaction, resulting in high-impact confidentiality loss while leaving integrity and availability unaffected. The attack vector requires only standard authenticated access to a system using the vulnerable printer driver.
Microsoft security advisories published at msrc.microsoft.com recommend applying the vendor-supplied updates referenced under CVE-2023-24883 to address the exposure. The associated EPSS score has remained steady at 0.1263 with no material post-disclosure increase.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-28873
Vulnerability Data
Microsoft PostScript and PCL6 Class Printer Driver Information Disclosure 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 directly prevent introduction of buffer over-read weaknesses.
Vulnerability identification processes can discover buffer over-read flaws via scanning or review.
Patching or replacing vulnerable software removes known instances of buffer over-read bugs.
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 can detect buffer over-reads before release.
Secure SDLC mandates input validation and bounds checking that can prevent buffer over-reads.
Application security requirements can specify buffer-size and bounds-checking rules.
Secure architecture principles include memory-safety and bounds-checking design choices.
Secure coding standards directly require bounds-checked buffer access, mitigating over-reads.