{"id":2162,"date":"2017-05-16T14:00:34","date_gmt":"2017-05-16T12:00:34","guid":{"rendered":"https:\/\/www.retarus.com\/blog\/en\/what-we-can-learn-from-%e2%80%9cwannacry%e2%80%9d"},"modified":"2024-05-07T19:07:33","modified_gmt":"2024-05-07T17:07:33","slug":"can-learn-wannacry","status":"publish","type":"post","link":"https:\/\/www.retarus.com\/blog\/en\/can-learn-wannacry\/","title":{"rendered":"What we can learn from \u201cWannaCry\u201d"},"content":{"rendered":"
On the past weekend the headlines were coming thick and fast about the ransomware known as \u201cWannaCry\u201d<\/a>, which had paralyzed computers around the globe \u2013 even impacting on critical infrastructure.<\/p>\n The malware exploited a long-known security gap in Windows, which the maker of the operating system, Microsoft, had already plugged in March. But as many computers had not yet been updated with the required patch or are running such old versions of Windows, that Microsoft no longer provides updates for them on a regular basis<\/a>, the ransomware also known as \u201cWannaCryptor\u201d, \u201cWannaCrypt\u201d, \u201cWana Decrypt0r\u201d or \u201cWCry\u201d spread like wildfire. The criminals demanded payment from high-profile victims such as\u00a0the UK\u2019s National Health Service (NHS)<\/a>, French car manufacturer Renault, Spanish carrier Telef\u00f3nica and Deutsche Bahn, if \u201conly\u201d their destination display boards<\/a>. However, the unknown originators of the attack have not been able to blackmail much money<\/a> out of their victims so far.<\/p>\n Note: This bot is watching the 3 wallets hard-coded into #WannaCry<\/a> ransomware. It tweets new payments as they occur, totals every two hours.<\/p>\n \u2014 actual ransom (@actual_ransom) 15. Mai 2017<\/a><\/p><\/blockquote>\n The USA and Canada were spared much impact from the outbreak due to their time zones. By the time North American workers were starting up their computers last Friday, a 22 year-old British security researcher had already discovered and activated a kill switch for \u201cWannaCry\u201d<\/a> more or less by chance \u2013 as soon as the malware found a certain URL\u00a0connected, it falsely assumed itself to be in a security test environment (“sandbox”) and ceased to be active. Since Sunday, however, a new variant without this kill switch has already been circulating<\/a>.<\/p>\n \u201cWannaCry\u201d spreads over computer networks, technically using an error in an older Microsoft incarnation of the SMB protocol (Server Message Block) for file, printing and other services in computer networks<\/a>. Knowledge of this error had been stashed away by the US military secret service, the NSA, until late summer 2016 when the hacker collective Shadow Brokers cyber-burgled them, making off with a whole raft of spying tools and intending to use them for financial gain.<\/p>\n One after another, the Shadow Brokers made the NSA tools available on the web. \u201cEternalblue\u201c, which provides the basis for \u201cWannaCry\u201d, was made public on Good Friday<\/a> of all days. From that point on, at least, it was really only a matter of time before a related attack would be sure to follow. Conspicuously, Microsoft had already called off the release of its monthly patch for February at short notice<\/a> and then put out an unusual number of error-corrections in March.<\/p>\n Microsoft apparently rates the SMB security gap as being extremely serious. Otherwise, it would be tough to explain the software giant wasting little time on Saturday to take the unusual step of breaking ranks by also providing patches for Windows versions which are still widely used yet no longer supported<\/a>, such as XP, Server 2003 or Windows 8.<\/p>\n\n
The attack was just a matter of time<\/h2>\n