4 ms·

> It's not "old Windows machines," it's XP to Server 2012. This is incorrect or at least misleading. Any machine still running Windows XP, is by any reasonabl

> It's not "old Windows machines," it's XP to Server 2012. This is incorrect or at least misleading. Any machine still running Windows XP, is by any reasonable definition, an "old Windows machine." Windows XP was first released in 2001, and actively supported with updates for 12 years. Windows XP hasn't been supported with critical security patches for over 3 years. Windows Server 2012 is under active support until Oct. 10, 2023, and was patched against this vulnerability in MS17-010. See the middle of the page here: https://technet.microsoft.com/en-us/library/security/ms17-010.aspx https://technet.microsoft.com/en-us/library/security/ms17-01... If your Windows Server 2012 machine fell victim to this ransomware, it was for the same reason as those running the newer Windows Server 2016 (also vulnerable to WannaCry): because someone didn't apply security patches in a timely manner. This ransomware was particularly damaging because of it's unusually wormable nature. (Ring 0, commonly enabled networking protocol, no user interaction required.)

boomboomsubban 9y ago
An XP computer is old, Windows 8.1 is one generation back. Both are vulnerable to this exploit. Yes, patches have been available for supported versions, I don't know how that makes anything I said wrong or misleading.
- johnmcd3 9y ago
  We agree about it being not JUST old Windows versions being affected. I replied to your comment because the "old" Windows XP having no patch available was significant here, and I read your comment as saying "old" windows versions were not proportionally more responsible for WannaCry's rapid spread. Windows XP is still the third largest version of Windows by current installed base (after Windows 10 and Windows 7). The fact that Windows XP remained unpatched was significant, as there is notable overlap between Windows machines that aren't getting new security updates (at least within a month or two of their release) and Windows machines still running Windows XP. This vulnerability was, in fact, unusually dangerous, relative to other Windows XP vulnerabilities that have come to light in the last 5 years, and the install base of the "older" Windows XP machines made a big difference in the ransomware's ability to spread.
  - boomboomsubban 9y ago
    The resources I see don't show XP as third, though I'm sceptical of anything based on user agent. And I can't find anything about how responsible they would be for the spread. I addressed that it wasn't "old" Windows because there is a crazy belief out there that this only hit XP.

boomboomsubban 9y ago

An XP computer is old, Windows 8.1 is one generation back. Both are vulnerable to this exploit. Yes, patches have been available for supported versions, I don't know how that makes anything I said wrong or misleading.

johnmcd3 9y ago
We agree about it being not JUST old Windows versions being affected. I replied to your comment because the "old" Windows XP having no patch available was significant here, and I read your comment as saying "old" windows versions were not proportionally more responsible for WannaCry's rapid spread. Windows XP is still the third largest version of Windows by current installed base (after Windows 10 and Windows 7). The fact that Windows XP remained unpatched was significant, as there is notable overlap between Windows machines that aren't getting new security updates (at least within a month or two of their release) and Windows machines still running Windows XP. This vulnerability was, in fact, unusually dangerous, relative to other Windows XP vulnerabilities that have come to light in the last 5 years, and the install base of the "older" Windows XP machines made a big difference in the ransomware's ability to spread.
- boomboomsubban 9y ago
  The resources I see don't show XP as third, though I'm sceptical of anything based on user agent. And I can't find anything about how responsible they would be for the spread. I addressed that it wasn't "old" Windows because there is a crazy belief out there that this only hit XP.