BrandPost: Insecure Protocols: SMBv1, LLMNR, NTLM, and HTTP

2 years ago 113
BOOK THIS SPACE FOR AD
ARTICLE AD

This article has been indexed from CSO Online

Four years ago, the WannaCry ransomware variant spread like wildfire, infecting and encrypting over 230,000 computers at public- and private-sector organizations worldwide, and inflicting hundreds of millions, if not billions, of dollars in damage. Less than two short months later, another ransomware attack, NotPetya, again ripped its way through global organizations, temporarily crippling the shipping industry and costing Maersk $300 million alone.

Both attacks exploited the same vulnerabilities in the Microsoft Server Message Block version one (SMBv1) protocol, an exploit known as EternalBlue.

And yet, today, four years after these devastating attacks took place, ExtraHop research found that SMBv1 is still surprisingly common in enterprise environments. Almost 70% had more than 10 devices still running the protocol. And it’s not just SMBv1.

To read this article in full, please click here

Read the original article: BrandPost: Insecure Protocols: SMBv1, LLMNR, NTLM, and HTTP

Read Entire Article