Re:Hackers exploited Word flaw for months while Microsoft in...
by nikanj on Thursday April 27, 2017 @03:33AM
(#14209840)
Next up on HN: extreme outrage after a botched security update breaks hundreds of millions of machines. Not all bugs can be fixed with a simple one-line fix, and the faster patches need to be cranked out, the lower quality they'll be.
Re:Hackers exploited Word flaw for months while Microsoft in...
by bitexploder on Thursday April 27, 2017 @06:58AM
(#14210566)
There was a simple settings change for a temp fix on this one too. When there is even a remote chance a bug is being exploited in the wild it needs to be disclosed. Corp IT can work around it almost always. Individuals can as well. This argument that "it's complex to patch" is a non-starter at best. We the users deserve the option to decide how to deal with it. Silent exploitation is how we all lose, even the vendor.
Re:Hackers exploited Word flaw for months while Microsoft in...
by BearGoesChirp on Thursday April 27, 2017 @10:11AM
(#14211562)
In which case the users need to be informed of the security risks they are taking by using that software. Hiding risks is not the answer.
Re:Hackers exploited Word flaw for months while Microsoft in...
by flukus on Thursday April 27, 2017 @03:47AM
(#14209881)
Well yeah, if a patch for a single application broke machines then the outrage would be deserved.
Re:Hackers exploited Word flaw for months while Microsoft in...
by geocar on Thursday April 27, 2017 @04:05AM
(#14209954)
Or maybe people stop shipping dogshit?
Re:Hackers exploited Word flaw for months while Microsoft in...
by grub5000 on Thursday April 27, 2017 @07:19AM
(#14210651)
It says it right in the article:
> "We performed an investigation to identify other potentially similar methods and ensure that our fix addresses [sic] more than just the issue reported," Microsoft said through a spokesman, who answered emailed
If MS had immediately patched CVE-2017-0199, only for someone to reverse the patch, discover an identical exploit somewhere else in the code and commence immediate abuse, people would crucify Microsoft.
From the article, it seems clear that Microsoft scheduled a public release of the patch as soon as it became clear it was being publicly exploited.
Looking at this story, it's possible that 90 days is almost too long and should be shortened. As time goes on, it's becoming more and more common for multiple parties to become aware of the same vulnerabilities. Not all of those parties have good intentions, as we see here. Shortening the window of exposure is key.