4 ms·
Is the implication supposed to be "Microsoft finally given 'okay' to fix zero-day now that it is no longer useful to Intelligence?"
by Lammy 6y ago
Is the implication supposed to be "Microsoft finally given 'okay' to fix zero-day now that it is no longer useful to Intelligence?"
- jlgaddis 6y agoThat was my first thought as well. Why else would they leave a known vulnerability unfixed for two years!? ISTM that someone else found out about the vulnerability out ("... which Microsoft acknowledged was actively being exploited.") -- perhaps after the NSA used it against them? -- so now that the cat is out of the bag and they are at risk of compromise -- they let Microsoft know and get it fixed.
- simiones 6y agoThis doesn't seem like the kind of vulnerability a security service would really care about. It's just about whether Windows does or doesn't show a nag prompt when trying to run the malicious file. I doubt there are any real systems where the only thing standing between the system being secure or not is Windows code signing.
- Lammy 6y agoWhy wouldn't a security service care about the ability to hide malicious executable payloads in files that are presented as having a higher-than-normal level of trustworthiness?
- jlgaddis 6y ago> This doesn't seem like the kind of vulnerability a security service would really care about. It's just about whether Windows does or doesn't show a nag prompt when trying to run the malicious file. And yet, if memory serves, they went to the trouble of stealing a code-signing certificate from a software development company so that they could do exactly that in an Iranian nuclear facility! Besides, even if this one weren't all that useful on its own, we've seen time and again how a few of these these "minor" vulnerabilities can be "chained" together, eventually resulting in a full compromise.
- cpgxiii 6y agoTo be specific, in that case the NSA wanted to install a malicious driver on Windows machines that required driver signature enforcement, so there was no other way to get a driver installed except to steal a certificate to sign their driver.
- Natsu 6y agoI'm surprised they could steal the certificate, as it should have been stored on an HSM.
- sukilot 6y agoMS doesn't care about fixing vulnerabilities in Oracle's JRE. Someone else found out? The bug was publicly announced 2 years ago. (Per the article we all read.)
- est31 6y agoI doubt it's been stalled because the government still wanted to exploit it. I think it's rather them not wanting past use to be detected. You can't always stop using a 0 day. If the binary is deployed somewhere on a air gapped host computer that still receives updates, it's out of your hands. How can you be sure the update will get there while the binary is still on the computer? You risk detection which is very very bad when you run an APT. The tiny part of the campaign can make an entire country or even group of countries adopt stricter policies. The government probably knows about enough holes to fix their malware promptly, but even if it does, it needs to "deploy" the fix all around the world otherwise it risks being noticed.
- Lammy 6y agoGrokking this doesn't make me okay with being a pawn in it by way of my choice of operating system :)
- CWuestefeld 6y agoThat doesn't seem to apply in this case. The vulnerability isn't masking the existence of the malware, it's only allowing its installer to run undetected (in some cases). Once the installer has done its job, they're golden. The vulnerability can be patched, but since the malware was already installed, it doesn't help the victim.
- imglorp 6y agoI have a more crackpot theory. Maybe intelligence is one reason (some revenue there?) but business is a second reason. For years, they depended on a variety of pressures to get people to upgrade to new OS's. First there's the whole office/client/server version dependency graph including CALs and DCs to force businesses to upgrade whole swaths. And of course bug fixes: why fix in a current version when they can tell you it's fixed in future, go buy that? Psychology. Then there's malware. Why would they sit by for around years (McAffe came out in 98!) watching the market get super-saturated with sketchy malware products and ignore security so badly? I think it's the same as above: upgrade now hoping it got fixed in the next new shiny. It's a human flaw. This makes me want to scream to closed source lovers. Why do you put yourself in this position? Open source users can audit and fix it themselves, pay someone to do it, chose another fork, or even discuss flaws openly without getting sued (cough oracle cough). Closed source users have no insight, no transparency, and no recourse but to suffer their abuser.
- gruez 6y ago>And of course bug fixes: why fix in a current version when they can tell you it's fixed in future, go buy that? Psychology. Only problem with that theory is that windows 10 has free updates, seemingly forever. It was released in 2015 (with a free upgrade program from prior versions), still supported to this date,and has no signs of stopping.
- imglorp 6y agoYes, something changed with 10 to a new business model, right? 1) drive more users toward cloud services, and 2) users are the other product.