{"id":15325,"date":"2019-05-15T10:45:14","date_gmt":"2019-05-15T18:45:14","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2019\/05\/15\/news-9074\/"},"modified":"2019-05-15T10:45:14","modified_gmt":"2019-05-15T18:45:14","slug":"news-9074","status":"publish","type":"post","link":"https:\/\/www.palada.net\/index.php\/2019\/05\/15\/news-9074\/","title":{"rendered":"Microsoft\u2019s First Windows XP Patch in Years Is a Very Bad Sign"},"content":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/media.wired.com\/photos\/5cdc3d8fc6a1822e416ba52e\/master\/pass\/Microsoft-wired-headers2400-B4.jpg\"\/><\/p>\n<p><strong>Credit to Author: Brian Barrett| Date: Wed, 15 May 2019 16:28:18 +0000<\/strong><\/p>\n<p><span class=\"lede\">This week, Microsoft <\/span>issued patches for 79 flaws across its platforms and products. One of them merits particular attention: a bug so bad that <a href=\"https:\/\/www.wired.com\/2017\/05\/still-use-windows-xp-prepare-worst\/\">Microsoft released a fix for it on Windows XP<\/a>, an operating system it officially abandoned five years ago.<\/p>\n<p>There\u2019s maybe no better sign of a vulnerability\u2019s severity; the last time Microsoft bothered to make a Windows XP fix publicly available was a little over two years ago, in the months before the <a href=\"https:\/\/www.wired.com\/2017\/05\/ransomware-meltdown-experts-warned\/\">WannaCry ransomware attack swept the globe<\/a>. This week\u2019s vulnerability has similarly devastating implications. In fact, Microsoft itself has drawn a direct parallel.<\/p>\n<p class=\"paywall\">\u201cAny future malware that exploits this vulnerability could propagate from vulnerable computer to vulnerable computer in a similar way as the WannaCry malware spread across the globe in 2017,\u201d Simon Pope, director of incident response for the Microsoft Security Response Center, <a href=\"https:\/\/blogs.technet.microsoft.com\/msrc\/2019\/05\/14\/prevent-a-worm-by-updating-remote-desktop-services-cve-2019-0708\/\" target=\"_blank\">wrote<\/a> in a statement announcing the patch Tuesday. \u201cIt is highly likely that malicious actors will write an exploit for this vulnerability and incorporate it into their malware.\u201d<\/p>\n<p class=\"paywall\">Microsoft is understandably withholding specifics about the bug, noting only that it hadn\u2019t seen an attack in action yet, and that the flaw relates to Remote Desktop Services, a feature that lets administrators take control of another computer that\u2019s on the same network.<\/p>\n<p class=\"paywall\">That small parcel of information, though, still gives potential attackers plenty enough to go on. \u201cEven mention that the area of interest is Remote Desktop Protocol is sufficient to uncover the vulnerability,\u201d says Jean Taggart, senior security researcher at security firm Malwarebytes.<\/p>\n<p class=\"paywall\">Expect that to happen quickly. \u201cThis will be fully automated in the next 24 to 48 hours and exploited by a worm,\u201d says Pieter Danhieux, CEO of secure coding platform Secure Code Warrior, referring to the class of malware that can propagate across a network without any human interaction, such as clicking the wrong link or opening the wrong attachment. Like the Blob, it just spreads.<\/p>\n<p class=\"paywall\">Once that worm gives hackers access to those devices, the possibilities are fairly limitless. Danhieux sees ransomware as a likely path; Taggart ticks off spam campaigns, DDoS, and data harvesting as possibilities. \u201cTake your pick,\u201d he adds. \u201cSuffice to say, a lot.\u201d<\/p>\n<p class=\"paywall\">The saving grace for all of this is that computers running Windows 8 and up aren\u2019t affected. But it\u2019s important not to underestimate the danger that Windows XP computers can still pose. Estimates vary, but analytics company Net Marketshare says that <a href=\"https:\/\/www.netmarketshare.com\/operating-system-market-share.aspx?options=%7B%22filter%22%3A%7B%22%24and%22%3A%5B%7B%22deviceType%22%3A%7B%22%24in%22%3A%5B%22Desktop%2Flaptop%22%5D%7D%7D%5D%7D%2C%22dateLabel%22%3A%22Trend%22%2C%22attributes%22%3A%22share%22%2C%22group%22%3A%22platformVersion%22%2C%22sort%22%3A%7B%22share%22%3A-1%7D%2C%22id%22%3A%22platformsDesktopVersions%22%2C%22dateInterval%22%3A%22Monthly%22%2C%22dateStart%22%3A%222018-05%22%2C%22dateEnd%22%3A%222019-04%22%2C%22segments%22%3A%22-1000%22%7D\" target=\"_blank\">3.57 percent<\/a> of all desktops and laptops still run Windows XP, which was first released in 2001. Conservatively, that&#x27;s still tens of millions of devices on Windows XP\u2014more than are running on the most recent version of MacOS. Moreover, you can assume with some confidence that almost none of those computers are ready for what\u2019s coming.<\/p>\n<p>&quot;When you\u2019re dealing with patching, it\u2019s a balancing act.&quot;<\/p>\n<p name=\"inset-left\" class=\"inset-left-component__el\">Richard Ford, Forcepoint<\/p>\n<p class=\"paywall\">Yes, plenty of Windows XP users are just folks who haven\u2019t dusted off their Dell Dimension tower since the last Bush administration. It seems unlikely that they&#x27;ll ever get around to installing this latest patch, especially given that you need to seek it out, and <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4500705\/customer-guidance-for-cve-2019-0708\" target=\"_blank\">download and install<\/a> it yourself.  It\u2019s hard enough to get people to update modern systems with their incessant nagging popups; one imagines that those still on Windows XP are in no rush to visit the Microsoft Update Catalog.<\/p>\n<p class=\"paywall\">More troubling, though, are the countless businesses and infrastructure concerns that still rely on Windows XP. As recently as 2016, even <a href=\"https:\/\/www.popularmechanics.com\/military\/weapons\/a19061\/britains-doomsday-subs-run-windows-xp\/\" target=\"_blank\">nuclear submarines<\/a> had it on board. For the most sensitive use cases\u2014like, say, nukes\u2014companies and governments pay Microsoft for continued security support. But the bulk of hospitals, businesses, and industrial plants that have Windows XP in their systems don\u2019t. And for many of those, upgrading\u2014or even installing a patch\u2014is more difficult than it might seem.<\/p>\n<p class=\"paywall\">\u201cPatching computers in industrial control networks is challenging because they often operate 24\/7, controlling large-scale physical processes like oil refining and electricity generation,\u201d says Phil Neray, vice president of industrial cybersecurity at CyberX, an IoT and ICS-focused security firm. Recent CyberX research indicates that more than half of industrial sites run unsupported Windows machines, making them potentially vulnerable. There\u2019s not much opportunity to test the impact of a patch on those types of systems, much less to interrupt operations to install them.<\/p>\n<p class=\"paywall\">That applies to health care systems, too, where the process of updating critical software could interrupt patient care. Other businesses run specialized software that\u2019s incompatible with more recent Windows releases; practically speaking, they\u2019re trapped on XP. And while the best way to protect yourself from this latest vulnerability\u2014and the countless others that now plague unsupported operating systems\u2014is to upgrade to the latest version of Windows, cash-strapped businesses tend to prioritize other needs.<\/p>\n<p class=\"paywall\">With any luck, Microsoft\u2019s extraordinary step of pushing a patch will spur many of them to action. It\u2019s hard to imagine a louder siren. \u201cWhen you\u2019re dealing with patching, it\u2019s a balancing act between the costs of patching and the costs of leaving it alone, or just asking users to upgrade,\u201d says Richard Ford, chief scientist at cybersecurity firm Forcepoint. \u201cThey would have a grasp of both the security risk\u2014and the reputational risk\u2014of not going after this vulnerability aggressively. Put those all together, and when the stars align it makes a lot of sense to provide the patch, quickly, safely, and even for operating systems that are out of support.\u201d<\/p>\n<p class=\"paywall\">The coming weeks and months should show, though, just how wide a gap exists between providing a patch and getting people to install it. An attack on Windows XP is at this point inevitable. And the fallout might be worse than you\u2019d have guessed.<\/p>\n<p class=\"related-cne-video-component__dek\">Ransomware. It&#39;s malware but worse. It takes the contents of your device hostage and demands Bitcoin as a, you guessed it, ransom. Here&#39;s how to avoid it and what to do if your laptop gets locked.<\/p>\n<p><a href=\"https:\/\/www.wired.com\/story\/microsoft-windows-xp-patch-very-bad-sign\" target=\"bwo\" >https:\/\/www.wired.com\/category\/security\/feed\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/media.wired.com\/photos\/5cdc3d8fc6a1822e416ba52e\/master\/pass\/Microsoft-wired-headers2400-B4.jpg\"\/><\/p>\n<p><strong>Credit to Author: Brian Barrett| Date: Wed, 15 May 2019 16:28:18 +0000<\/strong><\/p>\n<p>A very bad vulnerability in Windows XP could have serious ramifications, even with a patch.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[10378,10607],"tags":[714,21358],"class_list":["post-15325","post","type-post","status-publish","format-standard","hentry","category-security","category-wired","tag-security","tag-security-cyberattacks-and-hacks"],"_links":{"self":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/15325","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=15325"}],"version-history":[{"count":0,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/15325\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=15325"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=15325"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=15325"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}