Remote Code Execution Vulnerability for Windows Print Spooler which was discovered recently by Microsoft

Question

Many of you must have applied Microsoft recently released Out-of-Band patches for this which are KB5004958 & KB5004954 for Windows Server 2012 R2 , KB5004948 for Windows Server 2016 and KB5004945 for Windows 10 based machines. However, we are also reading articles which mention that the patches released by Microsoft are affecting the functionality of Zebra Printers. With our company having Zebra printers being actively used we have not applied those patches. Any of know if Microsoft have release modified version of patches?
https://www.bleepingcomputer.com/news/microsoft/windows-security-update-kb5004945-breaks-printing-on-zebra-printers/

Answer 1

Don’t worry, let’s check the Zebra official document. https://supportcommunity.zebra.com/s/article/000021051?language=en_US
From the document we can see that only printers running Windows 10 versions 21H1, 20H2, or 2004 and Windows Server 20H2 or 2004 may be affected. So you could install updates securely on your servers which run Windows Server 2012 R2 and Windows Server 2016.

Besides, there is a Fix in the document:
The links below connect to a Microsoft site with information on the steps being taken to address these issues across multiple versions of Windows:
Windows Version Link
Windows 10 21H1 https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-21h1#1647msgdesc
Windows 10 and Windows Server 20H2 https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-20h2#1647msgdesc
Windows 10 and Windows Server 2004 https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-2004#1647msgdesc

Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. Note Devices need to be restarted after configuring the special Group Policy.

-------------------------------------------------------------------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.
Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.