WannaCry
loreThe 2017 ransomware worm that spread through a leaked Windows exploit and crippled systems worldwide.
It used the EternalBlue SMB exploit to self-propagate, encrypting files and demanding Bitcoin, and hit hospitals, factories, and rail networks within hours. A researcher's accidental discovery of a kill-switch domain slowed it, but not before it caused billions in damage.
WannaCry spread in May 2017 using EternalBlue, an exploit for a Windows file-sharing flaw that had been developed by the NSA, leaked by a group calling itself the Shadow Brokers, and patched by Microsoft roughly two months before the outbreak. It encrypted files and demanded payment in bitcoin.
Its impact was disproportionate because it was a worm, not an email campaign: once inside a network it spread machine to machine without anyone clicking anything. Britain's National Health Service was among the most visible casualties, with appointments and procedures cancelled, and the reason was a familiar one, which is that systems too critical to take offline for patching are also too critical to lose.
Two details are worth remembering. A researcher stopped the outbreak almost by accident by registering a domain the malware checked, which functioned as a kill switch, and the ransom mechanism was so poorly built that paying frequently did not recover data. But the underlying lesson is about the patch gap: the fix existed, the exploit was public, and the interval between those two facts is where the entire event took place.
Also known as: WannaCry, WannaCrypt, WCry
Sources
- Microsoft Security Bulletin MS17-010, 'Security Update for Microsoft Windows SMB Server (4013389)', published 14 March 2017 - the patch for the SMBv1 flaw WannaCry exploited, two months before the May 2017 outbreak; it predates the outbreak and does not describe it
- The CVE Program's record for CVE-2017-0144, state PUBLISHED, published 2017-03-17: 'The SMBv1 server in Microsoft Windows ... allows remote attackers to execute arbitrary code via crafted packets, aka "Windows SMB Remote Code Execution Vulnerability."'