{"id":20580,"date":"2021-07-08T11:34:20","date_gmt":"2021-07-08T09:34:20","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=20580"},"modified":"2021-07-17T11:55:17","modified_gmt":"2021-07-17T09:55:17","slug":"the-chaos-printnightmare-emergency-update-july-6-7-2021","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2021\/07\/08\/the-chaos-printnightmare-emergency-update-july-6-7-2021\/","title":{"rendered":"The Chaos PrintNightmare Emergency Update (July 6\/7, 2021)"},"content":{"rendered":"

[German<\/a>]Microsoft has released out-of-band security updates for the PrintNightmare vulnerability (CVE-2021-1675) in the Windows Print Spooler service. But these updates seem to end in chaos – it reminds me on the Printer-Gate in March 2021, where Microsoft had to release a series of update fixes to close a printer vulnerability but still allow printing. I'll summarize a few points outside of Microsoft's documentation in this blog post. These range from the fact that the updates don't close the vulnerabilities, to installation issues and problems with Zebra label printers subsequently refusing to print.<\/p>\n

<\/p>\n

Updates for vulnerability CVE-2021-1675<\/h2>\n

\"\"In all versions of Windows a Remote Code Execution (RCE) vulnerability CVE-2021-1675 exists in the Windows Print Spooler service. This allows attackers to execute arbitrary code with SYSTEM privileges. After a proof of concept (PoC) became public, there were already first attacks against the vulnerability. I had reported early on about the vulnerability in the blog post PoC for Windows print spooler vulnerability public, high RCE risk<\/a>. Then, as of July 6 and 7, 2021, Microsoft also released unscheduled updates for supported versions of Windows (see links at the end of the article).<\/p>\n

Updates don't close all vulnerabilities<\/h2>\n

Part 1 of the drama lies in the fact that Microsoft has not managed to cleanly close the vulnerabilities in the Windows Print Spooler service. As of June 8, 2021, Microsoft had indeed closed a Local Privilege Escalation vulnerability in this service via the Windows security updates. At the beginning of July 2021, however, I had already pointed out in the blog post PoC for Windows print spooler vulnerability public, high RCE risk<\/a> that although the June 2021 patch eliminated a vulnerability, remote attacks on the Windows Print Spooler service via the CVE-2021-1675 vulnerability were still possible. Microsoft hadn't fixed all vulnerabilities.<\/p>\n

\"PrintNightmare-Patches\"<\/a><\/p>\n

Now Microsoft has released special updates for this vulnerability CVE-2021-1675. But a few days ago, other newly discovered vulnerabilities in the Windows Print Spooler service became known. And the out-of-band updates do not close these vulnerabilities, allowing attackers to exploit the changes made by the updates. German blog reader Carsten already pointed out the above tweet<\/a> in a comment.<\/p>\n

\"PrintNightmare<\/a><\/p>\n

The tweets<\/a> above again point this out, and colleagues at Bleeping Computer have addressed it here<\/a>, while The Hacker News tweeted it here<\/a> and has published this article<\/a>.<\/p>\n

\"PrintNightmare<\/a><\/p>\n

While the security updates released by Microsoft close a vulnerability, they can be easily bypassed. Mimikatz developer Benjamin Delpy writes in this tweet<\/a>, that the Local Privilege Escalation vulnerability (LPE) and the Remote Privilege Escalation vulnerability (RCE) can still be exploited.<\/p>\n

<\/p>\n

Delpy posted a flowchart of by-passing options in this tweet<\/a>. Microsoft's patches are working, but not really. Attacks on remote targets with \\ \\ in the URL are now prevented by a check, to be sure. However, if the attacker uses patterns like \\ ?? \\ in the UNC paths, attacks are still possible.<\/p>\n

Addendum:<\/strong> Microsoft has released a statement, claiming, that things raised the above are just a wrong configuration (see Microsoft on PrintNightmare vulnerability CVE-2021-34527: Windows is secure after patch<\/a>).<\/p><\/blockquote>\n

The updates cause problems<\/h2>\n

Actually, everything urges to install the unscheduled updates urgently. In the meantime, however, I have received initial feedback about problems, which I will briefly summarize.<\/p>\n

WSUS detection and installation problems<\/h3>\n

In this German comment<\/a> within my blog, a reader reported, that he has problems with detection in WSUS. Here's an excerpt:<\/p>\n

WSUS seems to have a detection bug again!
\n20H2 clients that already have KB5003690 (19042.1081) installed,
\nare not detected as \"needed\" target. Via MS the patch is found and installed.
\nI assume 20H2 clients with KB5004760 (19042.1082) are also affected.<\/p><\/blockquote>\n

I had pointed out the problem of the Servicing Stack Updates (SSU) integrated in the cumulative update (LCU) in the blog post Windows 10, the WSUS and the SSU+LCU detection chaos<\/a>. There are more voices on this topic in the linked comment thread – without the required SSU from May 2021, cumulative updates from June 2021 in WSUS probably can't be installed in Windows 10 version 2004 and higher. A solution for those affected can be found in this comment here on the blog.<\/p>\n

If the update Windows 10 2004-21H2 drops install error 0x80242017, this stands for WU_E_UH_NEW_SERVICING_STACK_REQUIRED, so the Mai 2021 SSU is missing. See this German comment<\/a> with the proposal, to download windows10.0-kb5004760-x86.msu<\/em>, then extract SSU-19041.1081-x86.cab <\/em>and try the command: Dism.exe \/online \/add-package:c:\\2\\SSU-19041.1081-x86.cab<\/em> to install the update. In case of a x64 system use the appropriate packages.<\/p><\/blockquote>\n

Zebra label printers can't print<\/h3>\n

Already directly after the release of the first out-of-band updates, German blog reader Sebastian got in touch in this comment<\/a> and writes:<\/p>\n

Hi,<\/p>\n

it looks like the update has \"killed\" the ticket printers for us – Windows 10 Pro x64 20H2<\/p>\n

Intermec EasyCoder F4 and PF4i … are just clarifying what is going on.<\/p>\n

Otherwise everything is ok so far (Canon, HP, Epson).<\/p><\/blockquote>\n

They wasn't able to use the label \/ ticket printer after installing the update. At German site heise I found a forum thread<\/a>, where users confirming striking Zebra label printers (D420, Zebra 2844, Intermec PF4i and PM43). It looks like only uninstalling the update in question can fix this problem.<\/p>\n

Addendum: Microsoft addressed the Zebra label printer issue, see Windows 10: Microsoft fixes Zebr & Dymo printer issues caused by update (e.g. KB5004945) via KIR<\/a>.<\/p><\/blockquote>\n

BlueScreens when printing?<\/h3>\n

On Facebook, I have received feedback from a IT specialist, telling me, that he has already had two customers with BlueScreens when printing through update KB5004945, as in March 2021. Details are not yet available – perhaps there the attention on it and give feedback here as a comment if necessary, if it occurs with you. Addendum:<\/strong> Got now a ton of feedback within the German blog, where users observed bluescreens with different printers.<\/p>\n

Non English KB articles are wrong<\/h3>\n

My advice to administrators is, to use the English kb articles about all PrintNightmare issues and updates. We have the situation, that the German kb article about \"Point and Print\" is simply wrong and gives advices, that deactivated the feature. In this German comment<\/a>, Stefan A. points out that Microsoft's German documentation on \"Point and Print\" is wrong. Hanspeter Holzer explicitly points this out again in the following tweet<\/a>.<\/p>\n

\"PrintNightmare<\/a><\/p>\n

Use the support article KB5005010: Restricting installation of new printer drivers after applying the July 6, 2021 updates<\/a>, to set the relevant policy entries.<\/p>\n

Attention with 0patch usage<\/h3>\n

Here in the blog I had discussed the micropatches from 0patch to close the vulnerability (see following link list). This solution was available before the Microsoft updates and probably does not have their consequences. So if you rely on 0patch, you should heed the following tweet<\/a> (thanks to Carsten).<\/p>\n

\"https:\/\/i.imgur.com\/fAIYFZx.png\"<\/a><\/p>\n

Similar articles:
\n<\/strong>Patchday: Windows 10-Updates (June 8, 2021)<\/a>
\nPoC for Windows print spooler vulnerability public, high RCE risk<\/a>
\nWindows Print Spooler Vulnerability (CVE-2021-1675, PrintNightmare) Confirmed by MS; CISA Warns<\/a>
\n0Patch Micropatches for PrintNightmare Vulnerability (CVE-2021-34527)<\/a>
\nOut-of-Band Update closes Windows PrintNightmare Vulnerability (July 6, 2021)<\/a>
\nPrintNightmare out-of-band update also for Windows Server 2012 and 2016 (July 7, 2021)<\/a>
\nThe Chaos PrintNightmare Emergency Update (July 6\/7, 2021)<\/a>
\nWindows 10: Microsoft fixes Zebr & Dymo printer issues caused by update (e.g. KB5004945) via KIR<\/a>
\nMicrosoft on PrintNightmare vulnerability CVE-2021-34527: Windows is secure after patch<\/a><\/p>\n

Windows vulnerability PrintNightmare: It's not over yet (July 15, 2021)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]Microsoft has released out-of-band security updates for the PrintNightmare vulnerability (CVE-2021-1675) in the Windows Print Spooler service. But these updates seem to end in chaos – it reminds me on the Printer-Gate in March 2021, where Microsoft had to release … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[580,22,2],"tags":[166,892,69,195,194],"class_list":["post-20580","post","type-post","status-publish","format-standard","hentry","category-security","category-update","category-windows","tag-issues","tag-printing","tag-security","tag-update","tag-windows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/20580","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=20580"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/20580\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=20580"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=20580"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=20580"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}