Windows Print Spooler Remote Code Execution Vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- Fix
- Fixed in 10.0.10240.18969, 10.0.14393.4470, 10.0.17763.2029, 10.0.19042.1083, 10.0.19044.1415, and 8 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Windows Print Spooler service on Windows systems, including Windows Server and Windows 10, is affected by this vulnerability, which could let an attacker run arbitrary code with SYSTEM privileges. An attacker who exploited it could then install programs, view, change, or delete data, or create new accounts with full user rights.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Microsoft Windows 10 Version 1507
From 10.0.10240.0 · fixed in 10.0.10240.18969
- Microsoft Windows 10 Version 1607
From 10.0.14393.0 · fixed in 10.0.14393.4470
- Microsoft Windows 10 Version 1809
From 10.0.17763.0 · fixed in 10.0.17763.2029
- Microsoft Windows 10 Version 1809
From 10.0.0 · fixed in 10.0.17763.2029
- Microsoft Windows 10 Version 20H2
From 10.0.0 · fixed in 10.0.19042.1083
- Microsoft Windows 10 Version 21H2
From 10.0.19044.0 · fixed in 10.0.19044.1415
- Microsoft Windows 10 Version 22H2
From 10.0.19045.0 · fixed in 10.0.19045.2251
- Microsoft Windows 11 version 21H2
From 10.0.22000.0 · fixed in 10.0.22000.318
- Microsoft Windows 11 version 22H2
From 10.0.22621.0 · fixed in 10.0.22621.674
- Microsoft Windows 8.1
From 6.3.0 · fixed in 6.3.9600.20046
- Microsoft Windows Server 2008 R2 Service Pack 1
From 6.1.7601.0 · fixed in 6.1.7601.25633
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)
From 6.1.7601.0 · fixed in 6.1.7601.25633
- Microsoft Windows Server 2008 Service Pack 2
From 6.0.6003.0 · fixed in 6.0.6003.21138
- Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)
From 6.0.6003.0 · fixed in 6.0.6003.21138
- Microsoft Windows Server 2012
From 6.2.9200.0 · fixed in 6.2.9200.23383
- Microsoft Windows Server 2012 (Server Core installation)
From 6.2.9200.0 · fixed in 6.2.9200.23383
- Microsoft Windows Server 2012 R2
From 6.3.9600.0 · fixed in 6.3.9600.20046
- Microsoft Windows Server 2012 R2 (Server Core installation)
From 6.3.9600.0 · fixed in 6.3.9600.20046
- Microsoft Windows Server 2016
From 10.0.14393.0 · fixed in 10.0.14393.4470
- Microsoft Windows Server 2016 (Server Core installation)
From 10.0.14393.0 · fixed in 10.0.14393.4470
- Microsoft Windows Server 2019
From 10.0.17763.0 · fixed in 10.0.17763.2029
- Microsoft Windows Server 2019 (Server Core installation)
From 10.0.17763.0 · fixed in 10.0.17763.2029
- Microsoft Windows Server 2022
From 10.0.20348.0 · fixed in 10.0.20348.230
- Microsoft Windows Server version 20H2
From 10.0.0 · fixed in 10.0.19042.1083