PrintNightmare (CVE-2021-34527): when the print service endangered domain controllers

A flaw in the Windows Print Spooler allowed code execution with SYSTEM rights, including on domain controllers. Why the print service should be off where it is not needed.

Publicly disclosed: 1 July 2021

In late June 2021 researchers accidentally published exploit code for a Windows Print Spooler flaw. On 1 July Microsoft assigned CVE-2021-34527, known as PrintNightmare, and released emergency updates on 6 July. An authenticated user could run code with SYSTEM privileges — and because the Print Spooler runs by default on almost every Windows machine, including domain controllers, it was an easy way to take over a whole Windows domain.

CVESeverityAffectedFixed in
CVE-2021-34527High, CVSS 8.8 (remote code execution, privilege escalation)All supported Windows versions with Print Spooler runningOut-of-band update of 6 July 2021 and later updates

How to protect

  1. Install Windows updates promptly, including the follow-up fixes for printer driver installation.
  2. Disable the Print Spooler service on servers that do not print, especially domain controllers.
  3. Allow only administrators to install printer drivers (Microsoft changed the default to this behaviour after PrintNightmare).
  4. Use dedicated print servers instead of printing from critical servers.

Every service that runs but is not needed is an open window. Close the ones you do not use.

Sources: Microsoft CVE-2021-34527, NVD CVE-2021-34527.

Need help with this? Contact CySec for a free consultation.


All articles

Need help with this?

Our engineers can review your current setup and propose concrete improvements.