Microsoft says the emergency security updates released at the start of the week correctly patch the PrintNightmare Print Spooler vulnerability for all supported Windows versions and urges users to start applying the updates as soon as possible.
This clarified guidance comes after security researchers tagged the patches as incomplete after finding that the OOB security updates could be bypassed in specific scenarios.
“Our investigation has shown that the OOB security update is working as designed and is effective against the known printer spooling exploits and other public reports collectively being referred to as PrintNightmare,” the Microsoft Security Response Center explains.
“All reports we have investigated have relied on the changing of default registry setting related to Point and Print to an insecure configuration.”
Microsoft has updated the PrintNightmare patch guidance and is now encouraging customers to update as soon as possible.
These are the correct steps required to patch this critical Windows Print Spooler RCE vulnerability as shared by Microsoft:
Additional information and further guidance are available in the KB5005010 support document and the CVE-2021-34527 security advisory.
Also Read: How to Choose a Penetration Testing Vendor
You can find detailed steps on how to install these emergency security updates in the support documents linked below:
If you cannot immediately install the security updates on your system(s), you can disable the Windows Print Spooler service to mitigate the PrintNightmare vulnerability temporarily.
Thursday night, Microsoft has also issued an emergency fix to address printing issues affecting Zebra and Dymo receipt or label printers due to changes introduced in the June 2021 cumulative update preview with the recently released KB5003690, KB5004760, and KB5004945 updates.
Also Read: The 5 Phases of Penetration Testing You Should Know
This fix is being rolled out via Microsoft’s Known Issue Rollback (KIR) feature, which pushes fixes for known issues through Windows Update and should reach most impacted systems within 24 hours (restarting the computer may also speed up the process.)