CVE-2022-41073
Memory Safety in Microsoft Windows 8.1
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2022-41073 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Microsoft Windows 8.1. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 18% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
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-2022-41073 is an elevation of privilege vulnerability in the Windows Print Spooler component, assigned CWE-787 for an out-of-bounds write condition. It affects supported Windows versions and carries a CVSS 3.1 base score of 7.8 reflecting local attack vector, low attack complexity, and low required privileges.
A local attacker with a valid low-privileged account can exploit the flaw to obtain SYSTEM-level privileges on the affected host. The vulnerability is triggered without user interaction once the attacker has access to the Print Spooler service.
Microsoft’s security update guide recommends installing the patches released in the November 2022 Patch Tuesday cycle; the same advisory is referenced by CISA’s Known Exploited Vulnerabilities catalog, confirming that the issue has been observed in active exploitation. The associated EPSS score remains low, with a recorded peak of 0.0328.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-44317
Vulnerability Data
Windows Print Spooler Elevation of Privilege Vulnerability
- CWE(s)
- KEV Date Added
- 08 November 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.
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 (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
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 can detect and prevent out-of-bounds write defects.
Secure development life cycle mandates practices that prevent out-of-bounds writes.
Application security requirements can specify bounds-checking and safe memory handling.
Secure architecture and engineering principles reduce the likelihood of buffer overflows.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.
Change management can enforce review gates that catch unsafe memory operations before deployment.