Microsoft Won’t Patch 20-Year-Old SMBv1 Vulnerability

Megalith

24-bit/48kHz
Joined
Aug 20, 2006
Messages
13,000
PSA: anyone who hasn’t already disabled SMBv1 may want to do just that, as another vulnerability has been found by security researchers at RiskSense: “SMBLoris” can lead to DoS attacks affecting every version of the SMB protocol and all versions of Windows since Windows 2000. Microsoft isn’t bothering to patch it, as they plan to remove the SMBv1 protocol in the Windows 10 Fall Creators Update, but everyone running older versions of Windows will remain affected.

RiskSense discovered the SMB vulnerability when analyzing EternalBlue, the leaked SMB exploit that is the source of the recent ransomware attacks. They disclosed the security flaw to Microsoft in June, but the company said that it won’t fix it. “The case offers no serious security implications and we do not plan to address it with a security update,” a Microsoft spokesperson told Threatpost. “For enterprise customers who may be concerned, we recommend they consider blocking access from the internet to SMBv1.”
 
Who wants to bet that if enough fuss is made they'll release a "correction" that they DO intend to patch this in Windows 7 and up?
 
Pretty shitty of them after they went back and patched XP and 2003 two months in a row...
 
I heard on the SANS podcast this morning that it can affect SMBv2/3 as well. Another user said that it can affect it even after disabling SMB all together (but, it may have been 'disabled', but a daemon was still running).

I think there will be more to this and Microsoft may change their course.
 
I've already, for free on my own time, corrected SMBV1 issue for family, friends, and business clients. Its pretty damn sad that Microsoft won't release a patch with eliminated the vulnerability all together.
 
They should issue a 'patch' that simply performs the proper steps as described in the KB article. Expecting millions of end users to wade thru the registry, group policy or running a script is lunacy. A large portion of users don't know what version of windows they are using.
 
You should be able to disable SMBv1 in windows 7 or above:

https://support.microsoft.com/en-us...-smbv1-smbv2-and-smbv3-in-windows-and-windows

I know of this page because you need to use this to enable newer smb on windows 7 or 8.


Exactly what I was thinking, SMBv1 is a no go around here and we aren't even connected to the internet.
Actually, for my storage systems I still get a scanned vulnerability because when it comes to SMB a NetApp filer just negotiates down to whatever is asked for. So if it get's an incoming SMBv1 request it just connects even though it is configured to allow SMBv2. So for them I just disable SMB entirely.
 
Back
Top