6 ms·
I saw this discussed on reddit, and I was surprised that there was so much confusion about how this happened. It wasn't just "network injection" - quite clearly
by hn_throwaway_99 6y ago
I saw this discussed on reddit, and I was surprised that there was so much confusion about how this happened. It wasn't just "network injection" - quite clearly (unfortunately very poorly described in the article) there was a vulnerability in iOS/Safari that allowed remote code execution; network injection alone wouldn't have been enough. Does anyone know what the CVE was that allowed this?
- VWWHFSfQ 6y agoAlso, does iOS have something similar to SELinux? I know it's not perfect, and there have been RCEs in Android as well. But I'm surprised there are still things out there like the original tiff jailbreak exploit that allows full root access to a person's device from just visiting a webpage.
- johncolanduoni 6y agoThe iOS equivalent would be the app sandboxing mechanism, which very heavily restricts kernel access from most of Safari (most importantly the process that is JITing javascript). It’s structured differently than SELinux and has some complications like entitlements that have led to vulnerabilities in the past, but it largely allows iOS to apply the same sort of app-level access control.
- saagarjha 6y agoiOS has a number of features that provide similar functionality; getting kernel level privileges on iOS requires multiple vulnerabilities to be chained together. It's not like RCE in the web browser process instantly compromises the entire system.
- nsajko 6y agoIt seems the iOS vulnerability itself is not known, from reading the Amnesty International report.
- roblabla 6y agoA code execution vulnerability isn't enough. To work on truly any website, they need: - A remote code execution vulnerability. There are almost certainly multiple vulnerabilities at play here, since long gone are the days where a single vuln gave arbitrary code execution. - a way to bypass the encryption/https, unless the remote code execution was on a layer before encryption (which seems unlikely). EDIT: Apparently the hack only works on non-encrypted websites. - Once remote code is achieved, they most certainly need a way to elevate privileges in order to make the hack more persistent and tap into other apps. There are most likely several CVEs at play here. The amount of effort that went into this hack is, frankly, terrifying.
- titanomachy 6y agoA huge amount of effort went into developing this hack. Then the company NSO productized the hack and sold it to governments.
- Biganon 6y agoAnd as soon as Apple fixes it, they're out of business? I really don't understand how any of that works.
- ObsoleteNerd 6y agoThey make enough money in between selling the tool and Apple patching the exploit to make it worthy, not to mention the amount of people who don’t do updates meaning the tool is still effective some of the time. Then the find/buy a new exploit and do it again.
- ChuckNorris89 6y agoFixes it? Apple could indeed fix some CVEs that they know about but every new OS/app/library release has the potential to introduce new CVEs that hackers can exploit. It's a moving target indeed but due to the increased complexity and questionable quality of modern software there's no way they're going out of business, quite the contrary.
- 6y ago
- greggman3 6y agoToo bad I can't run a different browser engine on iOS. In a monoculture everyone is exposed to the same vulnerabilities. If we had 3 or 4 browser engines running on iOS then the odds of a specific vulnerability affecting a single user go down. Further, there is competition for having the most secure browser. it's not controversial to say the 12 years ago IE, Firefox and Safari were pretty bad at security and Chrome in 2008 pushed them all to up their game. Apple's stance on browser engines is at best claiming security by obscurity. Either apps are sandboxed or they aren't. If they are then it would be safe to run any browser engine. If they aren't then having only one means users have no choice when that one fails.
- gbrown 6y agoPlus, no ublock origin for Safari.
- willyt 6y agoIt doesn’t protect you from vulnerabilities in things like, say the code in the system API which paints video frames to the screen, which is where a lot of these vulns seem to be. It wouldn’t have been 2008, didn’t safari and chrome mostly share WebKit for quite a long time anyway?
- greggman3 6y agoThey shared WebKit in 2008, but Chrome ran WebKit in its own process with no permissions and Safari did not, one of the reasons why Chrome was so much more secure. Glad I had the option to run Chrome and secure my browsing. I don't have that option on iOS. No team is allowed to even try to make things more secure.
- logicNSci 6y agoAnyone have a link to this? I want to post this Everytime someone claims Apple is best for security. We need logic to fight marketing.
- jeromegv 6y agoYou can still be the best and have security vulnerabilities. That proves absolutely nothing. I don’t know what kind of logic you are using. Are you implying that the best at security should never have had security vulnerabilities? If yes, what platform would that be?
- hugey010 6y agoCan you prove any options are "best"? If not, then marketing that way is dishonest at best.
- Thorrez 6y ago>Does anyone know what the CVE was that allowed this? >The malicious code even wipes crash logs, making it impossible to determine exactly what weaknesses were exploited to take over the phone, said Claudio Guarnieri, head of Amnesty International’s Security Lab, in an interview.
- yoran 6y agoThanks for clarifying. I honestly thought, how is the browser able to install spyware that "allows remote access to everything on the phone" (per the article), as the browser is supposed to be a sandboxed environment. I'm relieved it was "just" a vulnerability in iOS.