cve.bz

CVE-2021-34527 (PrintNightmare) Microsoft Windows Print Spooler Remote Code Execution Vulnerability

8.8 highKEVExploitEPSS 99.7%Fix available

Known as PrintNightmare

High (8.8) in Microsoft Windows. In CISA KEV since 2021-11-03, with known ransomware use. EPSS 99.7% estimated probability of exploitation activity in the next 30 days.

On this page
A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations. An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. UPDATE July 7, 2021: The security update for Windows Server 2012, Windows Server 2016 and Windows 10, Version 1607 have been released. Please see the Security Updates table for the applicable update for your system. We recommend that you install these updates immediately. If you are unable to install these updates, see the FAQ and Workaround sections in this CVE for information on how to help protect your system from this vulnerability. In addition to installing the updates, in order to secure your system, you must confirm that the following registry settings are set to 0 (zero) or are not defined (Note: These registry keys do not exist by default, and therefore are already at the secure setting.), also that your Group Policy setting are correct (see FAQ): HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers\PointAndPrint NoWarningNoElevationOnInstall = 0 (DWORD) or not defined (default setting) UpdatePromptSettings = 0 (DWORD) or not defined (default setting) Having NoWarningNoElevationOnInstall set to 1 makes your system vulnerable by design. UPDATE July 6, 2021: Microsoft has completed the investigation and has released security updates to address this vulnerability. Please see the Security Updates table for the applicable update for your system. We recommend that you install these updates immediately. If you are unable to install these updates, see the FAQ and Workaround sections in this CVE for information on how to help protect your system from this vulnerability. See also KB5005010: Restricting installation of new printer drivers after applying the July 6, 2021 updates. Note that the security updates released on and after July 6, 2021 contain protections for CVE-2021-1675 and the additional remote code execution exploit in the Windows Print Spooler service known as “PrintNightmare”, documented in CVE-2021-34527.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
99.7% (unchanged from 99.7% a week ago; 99.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2021-11-03, due 2022-05-03, known ransomware use
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2024-01-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2021-34527 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-34527?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-34527?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-34527 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 1507from 10.0.10240.0 before 10.0.10240.18969
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.4470
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.2029
Microsoft Windows 10 Version 1809from 10.0.0 before 10.0.17763.2029
Microsoft Windows 10 Version 20H2from 10.0.0 before 10.0.19042.1083
Microsoft Windows 10 Version 21H2from 10.0.19044.0 before 10.0.19044.1415
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.2251
Microsoft Windows 11 version 21H2from 10.0.22000.0 before 10.0.22000.318
Microsoft Windows 11 version 22H2from 10.0.22621.0 before 10.0.22621.674
Microsoft Windows 8.1from 6.3.0 before 6.3.9600.20046
Microsoft Windows Server 2008 R2 Service Pack 1from 6.1.7601.0 before 6.1.7601.25633
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)from 6.1.7601.0 before 6.1.7601.25633
Microsoft Windows Server 2008 Service Pack 2from 6.0.6003.0 before 6.0.6003.21138
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)from 6.0.6003.0 before 6.0.6003.21138
Microsoft Windows Server 2012from 6.2.9200.0 before 6.2.9200.23383
Microsoft Windows Server 2012 (Server Core installation)from 6.2.9200.0 before 6.2.9200.23383
Microsoft Windows Server 2012 R2from 6.3.9600.0 before 6.3.9600.20046
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.9600.0 before 6.3.9600.20046
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.4470
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.4470
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.2029
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.2029
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.230
Microsoft Windows Server version 20H2from 10.0.0 before 10.0.19042.1083

Public exploits

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

References

Check your stackJSON