CVE-2021-34481: Windows Print Spooler Remote Code Execution Vulnerability

Published Jul 15, 2021
·
Updated

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 August 10, 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. This security update changes the Point and Print default behavior; please see KB5005652.

Other sources

Windows Print Spooler Elevation of Privilege Vulnerability

Windows Print Spooler Remote Code Execution Vulnerability

Microsoft

Affected Software

55 affected componentsFixes available
Microsoft Windows 10
Microsoft Windows 10=20h2
Microsoft Windows 10=21h1
Microsoft Windows 10=1607
Microsoft Windows 10=1809
Microsoft Windows 10=1909
Microsoft Windows 10=2004
Microsoft Windows 7=sp1
Microsoft Windows 8.1
Microsoft Windows RT 8.1
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=r2-sp1
Microsoft Windows Server 2012
Microsoft Windows Server 2016
Microsoft Windows Server 2016=2004
Microsoft Windows Server 2019
Microsoft Windows Server 2008 R2<6.1.7601.25685
6.1.7601.25685
Microsoft Windows Server 2012<6.2.9200.23435
6.2.9200.23435
Microsoft Windows Server 2012 R2<6.3.9600.20094
6.3.9600.20094
Microsoft Windows Server 2012 R2<6.3.9600.20094
6.3.9600.20094
Microsoft Windows Server 2008<6.0.6003.21192
6.0.6003.21192
Microsoft Windows Server 2008<6.0.6003.21192
6.0.6003.21192
Microsoft Windows Server 2012<6.2.9200.23435
6.2.9200.23435
Microsoft Windows Server 2008<6.0.6003.21192
6.0.6003.21192
Microsoft Windows Server 2008 R2<6.1.7601.25685
6.1.7601.25685
Microsoft Windows Server 2008<6.0.6003.21192
6.0.6003.21192
Microsoft Windows RT 8.1<6.3.9600.20094
6.3.9600.20094
Microsoft Windows 10=1607
10.0.14393.4583
Microsoft Windows Server 2016<10.0.14393.4583
10.0.14393.4583
Microsoft Windows 7<6.1.7601.25685
6.1.7601.25685
Microsoft Windows 7<6.1.7601.25685
6.1.7601.25685
Microsoft Windows 8.1 for x64-based systems<6.3.9600.20094
6.3.9600.20094
Microsoft Windows 10=1607
10.0.14393.4583
Microsoft Windows Server 2016<10.0.14393.4583
10.0.14393.4583
Microsoft Windows Server=20H2
10.0.19042.1165
Microsoft Windows 10<10.0.10240.19022
10.0.10240.19022
Microsoft Windows 8.1 for 32-bit systems<6.3.9600.20094
6.3.9600.20094
Microsoft Windows 10<10.0.10240.19022
10.0.10240.19022
Microsoft Windows 10=20H2
10.0.19042.1165
Microsoft Windows 10=20H2
10.0.19042.1165
Microsoft Windows Server=2004
10.0.19041.1165
Microsoft Windows 10=1909
10.0.18363.1734
Microsoft Windows 10=1909
10.0.18363.1734
Microsoft Windows 10=1909
10.0.18363.1734
Microsoft Windows 10=2004
10.0.19041.1165
Microsoft Windows 10=2004
10.0.19041.1165
Microsoft Windows Server 2019<10.0.17763.2114
10.0.17763.2114
Microsoft Windows 10=21H1
10.0.19043.1165
Microsoft Windows 10=21H1
10.0.19043.1165
Microsoft Windows 10=21H1
10.0.19043.1165
Microsoft Windows 10=1809
10.0.17763.2114
Microsoft Windows Server 2019<10.0.17763.2114
10.0.17763.2114
Microsoft Windows 10=2004
10.0.19041.1165
Microsoft Windows 10=1809
10.0.17763.2114
Microsoft Windows 10=1809
10.0.17763.2114

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.1.7601.25685Patch KB5005089
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.2.9200.23435Patch KB5005094
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.20094Patch KB5005106
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.0.6003.21192Patch KB5005095
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.20094Patch KB5005076
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.4583Patch KB5005043
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19042.1165Patch KB5005033
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.10240.19022Patch KB5005040
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19041.1165Patch KB5005033
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.18363.1734Patch KB5005031
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19043.1165Patch KB5005033
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.2114Patch KB5005030
  13. Upgrade

    Upgrade Windows Print Spooler to a version that resolves this vulnerability.

    Patch KB5005652
  14. Compensating control

    Review and implement the Point and Print default-behavior changes described in KB5005652 associated with this security update.

Event History

Jul 15, 2021
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·02:00 PM
Affected Software
Updated
via Microsoft·02:00 PM
Description
Jul 16, 2021
CVE Published
via MITRE·08:19 PM
Data Sourced
via MITRE·08:19 PM
DescriptionSeverity
Data Sourced
via NVD·09:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 29, 2025
News Published
via Dark Reading·10:10 PM
Jan 30, 2025
News Published
via Dark Reading·05:03 AM
Feb 4, 2025
Known Exploited
02:29 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2021-34481?

The severity of CVE-2021-34481 is rated as critical due to its potential for remote code execution.

2

How do I fix CVE-2021-34481?

To fix CVE-2021-34481, it is recommended to apply the latest security patches provided by Microsoft for affected Windows versions.

3

Which Windows versions are affected by CVE-2021-34481?

CVE-2021-34481 affects multiple versions of Windows, including Windows 7, 8.1, 10, and various Windows Server editions.

4

What type of attack can be executed using CVE-2021-34481?

An attacker can exploit CVE-2021-34481 to run arbitrary code with elevated privileges on the affected system.

5

Is there a workaround for CVE-2021-34481?

Currently, the best approach is to apply patches, as specific workarounds for CVE-2021-34481 may not fully mitigate the vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203