Microsoft emergency fix for "PrintNightmare” vulnerability

[TSwizzle]

FFS Microsoft !

Microsoft is starting to roll out patches for the “PrintNightmare” vulnerability, which can help a hacker remotely take over a Windows PC.

The patches target most versions of Windows, including the latest version of Windows 10 21H1, and Windows 7 Service Pack 1. However, the company has yet to release the security fixes for Windows 10 Version 1607, Windows Server 2016, and Windows Server 2012.

PC Magazine

This blows.

 

[Tigers!]

FFS Microsoft !

Microsoft is starting to roll out patches for the “PrintNightmare” vulnerability, which can help a hacker remotely take over a Windows PC.

The patches target most versions of Windows, including the latest version of Windows 10 21H1, and Windows 7 Service Pack 1. However, the company has yet to release the security fixes for Windows 10 Version 1607, Windows Server 2016, and Windows Server 2012.

PC Magazine

This blows.

Disappointing that years later Microsoft is still finding such issues.
Had to turn off the print spooler on our 2 DCs and load the patch onto our 8 servers. SEEMS OK.

 

[funinspace]

FFS Microsoft !

Microsoft is starting to roll out patches for the “PrintNightmare” vulnerability, which can help a hacker remotely take over a Windows PC.

The patches target most versions of Windows, including the latest version of Windows 10 21H1, and Windows 7 Service Pack 1. However, the company has yet to release the security fixes for Windows 10 Version 1607, Windows Server 2016, and Windows Server 2012.

PC Magazine

This blows.

Yeah, sounds like standard Microslop. However, most people's PCs are not really at risk at home or in an office that hasn't been infiltrated already.

From your article:

Fortunately, the attack can only be pulled off if the hacker has access to your PC’s internet network. The bigger danger is for enterprises, which operate hundreds, if not thousands of computers, across their networks. As a result, a hacker who infiltrates one PC on a corporate network could exploit PrintNightmare to unleash havoc.

If you are using a public network, I'd turn off your print spooler before connecting, which really is pretty easy to disable/enable via Powershell. See details here:
https://www.bleepingcomputer.com/ne...te-print-spooler-vulnerability-on-windows-10/
Easy Powershell commands:
>Stop-Service -Name Spooler -Force
To restart:
>Start-Service -Name Spooler
Check status:
>Get-Service -Name Spo*