Saturday, February 22, 2014

That Urgent iOS Security Update? Probably Thanks To NSA

★ On the Timing of iOS's SSL Vulnerability and Apple's 'Addition' to the NSA's PRISM Program
These guys (NSA) are out of control and need to be reined in.  They are weakening everyone's security so that they can spy on all of us, all of the time.
Jeffrey Grossman, on Twitter: I have confirmed that the SSL vulnerability was introduced in iOS 6.0. It is not present in 5.1.1 and is in 6.0. iOS 6.0 shipped on 24 September 2012. 
According to slide 6 in the leaked PowerPoint deck on NSA's PRISM program, Apple was "added" in October 2012. These three facts prove nothing; it's purely circumstantial. But the shoe fits. Sure would be interesting to know who added that spurious line of code to the file. Conspiratorially, one could suppose the NSA planted the bug, through an employee mole, perhaps. Innocuously, the Occam's Razor explanation would be that this was an inadvertent error on the part of an Apple engineer. It looks like the sort of bug that could result from a merge gone bad, duplicating the goto fail; line. Once in place, the NSA wouldn't even have needed to find the bug by manually reading the source code. All they would need are automated tests using spoofed certificates that they run against each new release of every OS. Apple releases iOS, the NSA's automated spoofed certificate testing finds the vulnerability, and boom, Apple gets "added" to PRISM. Or, maybe nothing, and this is all a coincidence. 
I see five levels of paranoia: 
1 - Nothing. The NSA was not aware of this vulnerability. 
2 - The NSA knew about it, but never exploited it. 
3 - The NSA knew about it, and exploited it. 
4 - NSA itself planted it. 
5 - Apple, complicit with the NSA, added it. 
Me, I'll go as far as #3. In fact, I think that's actually the optimistic scenario — because we know from the PRISM slides that the NSA claims some ability to do what this vulnerability would allow. So if this bug, now closed, is not what the NSA was exploiting, it means there might exist some other vulnerability that remains open.
I'd say 3 at the least - more likely 4.

No comments: