{"id":46750,"date":"2022-05-20T13:00:10","date_gmt":"2022-05-20T13:00:10","guid":{"rendered":"https:\/\/www.threatshub.org\/blog\/microsoft-patches-the-patch-that-broke-windows-authentication\/"},"modified":"2022-05-20T13:00:10","modified_gmt":"2022-05-20T13:00:10","slug":"microsoft-patches-the-patch-that-broke-windows-authentication","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/microsoft-patches-the-patch-that-broke-windows-authentication\/","title":{"rendered":"Microsoft patches the patch that broke Windows authentication"},"content":{"rendered":"

Microsoft has released an out-of-band patch to deal with an authentication issue that was introduced in the May 10 Windows update.<\/p>\n

Elizabeth Tyler, cyber security consultant on Microsoft’s Detection and Response Team, confirmed the fix to worried administrators early this morning.<\/p>\n

\n

Yes, fixed and released 19 May.
\n
CU:
\n
WS 2022: KB5015013
\n
WS, version 20H2: KB5015020
\n
WS 2019: KB5015018
\n
WS 2016: KB5015019
\n
Standalone:
\n
WS 2012 R2: KB5014986
\n
WS 2012: KB5014991
\n
WS 2008 R2 SP1: KB5014987
\n
WS 2008 SP2: KB5014990<\/p>\n

\u2014 Elizabeth Tyler (@MSetyler) May 20, 2022<\/a><\/p><\/blockquote>\n

Multiple administrators complained<\/a> last week that after installing the May 10 patch, they experienced authentication failures across several systems.<\/p>\n

Tyler said<\/a> at the time: “We know the root cause is the subject name is incorrectly used to map the cert to a machine account in AD rather than the DNSHostname in the subject alternative name on DCs that have installed 5b and we’re working it.”<\/p>\n

An entry then turned up in the lengthy list of known issues for the patch in which Microsoft warned that, after installing the May 10 patch on domain controllers, there might be issues with some services.<\/p>\n