CriticalCVE-2022-41073

    Windows Print Spooler Elevation of Privilege Vulnerability (CVE-2022-41073)

    Published Last modified In CISA KEV since Sources: CVE.org

    What is affected, what to do

    Windows Print Spooler Elevation of Privilege Vulnerability

    The vulnerability is being actively exploited; treat it as a priority. CISA lists it as used in ransomware campaigns. Update Microsoft Windows 10 Version 1507 to version 10.0.10240.19567, Microsoft Windows 10 Version 1607 to version 10.0.14393.5501, Microsoft Windows 10 Version 1809 to version 10.0.17763.3650. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Microsoft Windows 10 Version 1507 lt 10.0.10240.0..10.0.10240.19567
    • Microsoft Windows 10 Version 1607 lt 10.0.14393.0..10.0.14393.5501
    • Microsoft Windows 10 Version 1809 lt 10.0.17763.0..10.0.17763.3650
    • Microsoft Windows 10 Version 20H2 lt 10.0.0..10.0.19042.2251
    • Microsoft Windows 10 Version 21H1 lt 10.0.0..10.0.19043.2251
    • Microsoft Windows 10 Version 21H2 lt 10.0.19043.0..10.0.19044.2251
    • Microsoft Windows 10 Version 22H2 lt 10.0.19045.0..10.0.19045.2251
    • Microsoft Windows 11 version 21H2 lt 10.0.0..10.0.22000.1219
    • Microsoft Windows 11 version 22H2 lt 10.0.22621.0..10.0.22621.819
    • Microsoft Windows 7 lt 6.1.0..6.1.7601.26221
    • Microsoft Windows 7 Service Pack 1 lt 6.1.0..6.1.7601.26221
    • Microsoft Windows 8.1 lt 6.3.0..6.3.9600.20671
    • Microsoft Windows Server 2008 Service Pack 2 lt 6.0.6003.0..6.0.6003.21768
    • Microsoft Windows Server 2008 R2 Service Pack 1 lt 6.1.7601.0..6.1.7601.26221
    • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) lt 6.1.7601.0..6.1.7601.26221
    • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) lt 6.0.6003.0..6.0.6003.21768
    • Microsoft Windows Server 2012 lt 6.2.9200.0..6.2.9200.23968
    • Microsoft Windows Server 2012 (Server Core installation) lt 6.2.9200.0..6.2.9200.23968
    • Microsoft Windows Server 2012 R2 lt 6.3.9600.0..6.3.9600.20671
    • Microsoft Windows Server 2012 R2 (Server Core installation) lt 6.3.9600.0..6.3.9600.20671
    • Microsoft Windows Server 2016 lt 10.0.14393.0..10.0.14393.5501
    • Microsoft Windows Server 2016 (Server Core installation) lt 10.0.14393.0..10.0.14393.5501
    • Microsoft Windows Server 2019 lt 10.0.17763.0..10.0.17763.3650
    • Microsoft Windows Server 2019 (Server Core installation) lt 10.0.17763.0..10.0.17763.3650
    • Microsoft Windows Server 2022 lt 10.0.20348.0..10.0.20348.1249
    Fixed in
    • Microsoft Windows 10 Version 1507 10.0.10240.19567
    • Microsoft Windows 10 Version 1607 10.0.14393.5501
    • Microsoft Windows 10 Version 1809 10.0.17763.3650
    • Microsoft Windows 10 Version 20H2 10.0.19042.2251
    • Microsoft Windows 10 Version 21H1 10.0.19043.2251
    • Microsoft Windows 10 Version 21H2 10.0.19044.2251
    • Microsoft Windows 10 Version 22H2 10.0.19045.2251
    • Microsoft Windows 11 version 21H2 10.0.22000.1219
    • Microsoft Windows 11 version 22H2 10.0.22621.819
    • Microsoft Windows 7 6.1.7601.26221
    • Microsoft Windows 7 Service Pack 1 6.1.7601.26221
    • Microsoft Windows 8.1 6.3.9600.20671
    • Microsoft Windows Server 2008 Service Pack 2 6.0.6003.21768
    • Microsoft Windows Server 2008 R2 Service Pack 1 6.1.7601.26221
    • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) 6.1.7601.26221
    • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) 6.0.6003.21768
    • Microsoft Windows Server 2012 6.2.9200.23968
    • Microsoft Windows Server 2012 (Server Core installation) 6.2.9200.23968
    • Microsoft Windows Server 2012 R2 6.3.9600.20671
    • Microsoft Windows Server 2012 R2 (Server Core installation) 6.3.9600.20671
    • Microsoft Windows Server 2016 10.0.14393.5501
    • Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.5501
    • Microsoft Windows Server 2019 10.0.17763.3650
    • Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.3650
    • Microsoft Windows Server 2022 10.0.20348.1249

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.8

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org

    2.4 %

    EPSS score

    Moderate — model estimates 1-10% exploitation likelihood.

    Source: FIRST EPSS, percentile 83.7

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    221.75 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploited
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    2.4 %
    Moderate — model estimates 1-10% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    83.7
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 22 December 2023
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-787

    Response and mitigation

    Why act now?

    Prioritisation rationale

    CVE-2022-41073 was patched as a zero-day in November 2022 and is a classic post-exploitation building block. Any low-privileged local foothold can be turned into SYSTEM with low complexity and no user interaction. CISA flags known ransomware use, which fits the familiar chain of phishing or loader, then privilege escalation, then credential dumping, then encryption. Overall exploitation likelihood is moderate because local access is a prerequisite. Even so, organisations with large client fleets, lagging builds or the spooler running on servers should treat it as high priority — especially on any host already showing signs of initial access.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Deploy the November 2022 cumulative update (Patch Tuesday, 2022-11-08). Minimum builds per the context: Windows 10 1507 → 10.0.10240.19567, 1607 → 10.0.14393.5501, 1809 → 10.0.17763.3650, 20H2/21H1/21H2/22H2 → 10.0.19042/19043/19044/19045.2251, Windows 11 21H2 → 10.0.22000.1219. Look up the KB number for each build in the MSRC advisory for CVE-2022-41073. Windows Server editions are not listed in the context; confirm their exposure in the vendor advisory.
      • Find unpatched hosts. Query EDR, Intune or SCCM for CurrentBuild + UBR (HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion) and flag anything below the minimum build as high risk.
      • Disable the Print Spooler wherever printing isn't required. Start with domain controllers, Tier-0/Tier-1 servers and jump hosts: Stop-Service Spooler -Force; Set-Service Spooler -StartupType Disabled.
      • Patch hosts with recent initial-access alerts first. This is a local privilege escalation. Endpoints with fresh phishing, loader or infostealer detections go to the front of the queue; hunt them for SYSTEM processes parented by spoolsv.exe.
      • Isolate any host suspected of compromise. Then rotate local admin passwords (LAPS) and any cached domain credentials, since SYSTEM access gives an attacker LSASS.

    2. Runbook step 2

      Mitigation layers

      • Configuration: Set the GPO "Allow Print Spooler to accept client connections" to Disabled on everything except dedicated print servers.
      • Driver installation: Set HKLM\Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint\RestrictDriverInstallationToAdministrators = 1 and restrict Point and Print to approved print servers.
      • Application control (WDAC/AppLocker): Block unsigned DLLs in C:\Windows\System32\spool\drivers\ and ...\spool\PRINTERS\. Use an EDR policy to deny child processes of spoolsv.exe, with an allowlist for legitimate driver helpers.
      • IAM/least privilege: Strip local admin rights and enforce LAPS. Enable Credential Guard and LSA protection (RunAsPPL) to blunt the credential-theft step that usually follows escalation.
      • Network segmentation: Allow SMB (445/tcp) and RPC (135/tcp plus dynamic ports) to print servers only from client VLANs, and block client-to-client print shares. This limits lateral movement after a successful escalation.

    3. Runbook step 3

      Detection rules

      • Sysmon EID 1 / Security 4688 – process ancestry: spoolsv.exe spawning cmd.exe, powershell.exe, rundll32.exe or whoami.exe. KQL: DeviceProcessEvents | where InitiatingProcessFileName =~ "spoolsv.exe" and FileName in~ ("cmd.exe","powershell.exe","rundll32.exe","whoami.exe")
      • Sysmon EID 11 – file creation: DLL/EXE files written under \spool\drivers\ or \spool\PRINTERS\ by any process other than spoolsv.exe or TrustedInstaller.
      • Sysmon EID 7 – image load: spoolsv.exe loading an unsigned DLL or one from outside System32. Sigma shape: Image|endswith: '\spoolsv.exe' AND Signed: 'false'
      • Sysmon EID 13 – registry: Writes to HKLM\SYSTEM\CurrentControlSet\Control\Print\Environments\*\Drivers or ...\Print\Monitors by non-system processes.
      • PrintService logs: Microsoft-Windows-PrintService/Admin EID 808 (plugin load failure) and Operational EID 316 (driver install) outside change windows; correlate with new SYSTEM logons (4624, type 5).

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Windows Print Spooler Elevation of Privilege Vulnerability

    Source: CISA KEV Catalog, NVD (NIST), cvelistv5, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    MicrosoftWindows 10 Version 1507
    • 10.0.10240.0 – < 10.0.10240.19567
    • 10.0.10240.19567
    MicrosoftWindows 10 Version 1607
    • 10.0.14393.0 – < 10.0.14393.5501
    • 10.0.14393.5501
    MicrosoftWindows 10 Version 1809
    • 10.0.17763.0 – < 10.0.17763.3650
    • 10.0.17763.3650
    MicrosoftWindows 10 Version 20H2
    • 10.0.0 – < 10.0.19042.2251
    • 10.0.19042.2251
    MicrosoftWindows 10 Version 21H1
    • 10.0.0 – < 10.0.19043.2251
    • 10.0.19043.2251
    MicrosoftWindows 10 Version 21H2
    • 10.0.19043.0 – < 10.0.19044.2251
    • 10.0.19044.2251
    MicrosoftWindows 10 Version 22H2
    • 10.0.19045.0 – < 10.0.19045.2251
    • 10.0.19045.2251
    MicrosoftWindows 11 version 21H2
    • 10.0.0 – < 10.0.22000.1219
    • 10.0.22000.1219
    MicrosoftWindows 11 version 22H2
    • 10.0.22621.0 – < 10.0.22621.819
    • 10.0.22621.819
    MicrosoftWindows 7
    • 6.1.0 – < 6.1.7601.26221
    • 6.1.7601.26221
    MicrosoftWindows 7 Service Pack 1
    • 6.1.0 – < 6.1.7601.26221
    • 6.1.7601.26221
    MicrosoftWindows 8.1
    • 6.3.0 – < 6.3.9600.20671
    • 6.3.9600.20671
    MicrosoftWindows Server 2008 R2 Service Pack 1
    • 6.1.7601.0 – < 6.1.7601.26221
    • 6.1.7601.26221
    MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)
    • 6.1.7601.0 – < 6.1.7601.26221
    • 6.1.7601.26221
    MicrosoftWindows Server 2008 Service Pack 2
    • 6.0.6003.0 – < 6.0.6003.21768
    • 6.0.6003.21768
    MicrosoftWindows Server 2008 Service Pack 2 (Server Core installation)
    • 6.0.6003.0 – < 6.0.6003.21768
    • 6.0.6003.21768
    MicrosoftWindows Server 2012
    • 6.2.9200.0 – < 6.2.9200.23968
    • 6.2.9200.23968
    MicrosoftWindows Server 2012 (Server Core installation)
    • 6.2.9200.0 – < 6.2.9200.23968
    • 6.2.9200.23968
    MicrosoftWindows Server 2012 R2
    • 6.3.9600.0 – < 6.3.9600.20671
    • 6.3.9600.20671
    MicrosoftWindows Server 2012 R2 (Server Core installation)
    • 6.3.9600.0 – < 6.3.9600.20671
    • 6.3.9600.20671
    MicrosoftWindows Server 2016
    • 10.0.14393.0 – < 10.0.14393.5501
    • 10.0.14393.5501
    MicrosoftWindows Server 2016 (Server Core installation)
    • 10.0.14393.0 – < 10.0.14393.5501
    • 10.0.14393.5501
    MicrosoftWindows Server 2019
    • 10.0.17763.0 – < 10.0.17763.3650
    • 10.0.17763.3650
    MicrosoftWindows Server 2019 (Server Core installation)
    • 10.0.17763.0 – < 10.0.17763.3650
    • 10.0.17763.3650
    MicrosoftWindows Server 2022
    • 10.0.20348.0 – < 10.0.20348.1249
    • 10.0.20348.1249

    Vendors and products

    Affected operating systems

    Affected operating systems
    Windowsmicrosoftwindows_10_1507—
    Windowsmicrosoftwindows_10_1607—
    Windowsmicrosoftwindows_10_1809—
    Windowsmicrosoftwindows_10_20h2—
    Windowsmicrosoftwindows_10_21h1—
    Windowsmicrosoftwindows_10_21h2—
    Windowsmicrosoftwindows_10_22h2—
    Windowsmicrosoftwindows_11_21h2—
    Windowsmicrosoftwindows_11_22h2—
    Windowsmicrosoftwindows_7—
    Windowsmicrosoftwindows_8.1—
    Windowsmicrosoftwindows_server_2008r2
    Windowsmicrosoftwindows_server_2008—
    Windowsmicrosoftwindows_server_2012r2
    Windowsmicrosoftwindows_server_2012—
    Windowsmicrosoftwindows_server_2016—
    Windowsmicrosoftwindows_server_2019—
    Windowsmicrosoftwindows_server_2022—

    Weakness classes (CWE)

    • CWE-787Out-of-bounds Write

      Base

      The product writes data past the end, or before the beginning, of the intended buffer.

      Entry at MITRE CWE-787

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    Packet StormMicrosoft Windows Privilege Escalation (opens in a new tab)packetstormsecurity.comPoC (publicly reported)reported, not verified—

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedMicrosoft

      1 individual change: Affected versions (publisher)

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)changed
      Windows 10 Version 1809, Windows 10 Version 1809, Windows Server 2019 (+24)
      Windows 10 Version 1507, Windows 10 Version 1607, Windows 10 Version 1809 (+24)

      Source identifier: secure@microsoft.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2022-41073
    <a href="https://intel.neosec.eu/en/cve/CVE-2022-41073"><img src="https://intel.neosec.eu/badge/cve/CVE-2022-41073.svg?lang=en" alt="CVE-2022-41073 – NEOSEC Intel" height="20"></a>