Live data from Hacker News

NSO group iPhone zero-click, zero-day exploit captured in the wild

citizenlab.ca

91–100 of 886 posts

Re: NSO group iPhone zero-click, zero-day exploit captured in the wild

#91
post #3

> The exploit involved PassKit attachments containing malicious images sent from an attacker iMessage account to the victim. Man, iMessage is a security disaster for Apple. No matter how much work they do in other areas, it seems like they'll paying for a while for their decisions around the iMessage architecture.

iMessage is overall a lot more complicated and integrated than I like it to be. Want to switch accounts, you gotta log your entire user or device out of iCloud. Logging back in will often create issues. Using old Mac/iPhone OS versions creates issues. Messages and attachments are received separately by different devices, and weird things happen when one device is out of space. Deleting messages or blocking senders is per-device. Different devices might miss some messages or even get them out of order. A device waking from sleep often gets messages delayed by minutes (like email), and you're notified a second time for them. And lastly, the "effective. Power لُلُصّبُلُلصّبُررً ॣ ॣh ॣ ॣ 冗" vulnerabilities.

Compared to Facebook Messenger where there's one consistent state in the master server and neatly sandboxed web or iPhone app calling it. And yeah, I know these are partially by-products of e2ee vs traditional, and nobody else has really done e2ee messaging with multiple devices.

Re: NSO group iPhone zero-click, zero-day exploit captured in the wild

#92

Wow this sounds like stagefright was way back when. So for those keeping score, is Android now ahead of iOS in this aspect of security?

I never hear about Android vulnerabilities, but it seems wrong to say they haven't existed.

Re: NSO group iPhone zero-click, zero-day exploit captured in the wild

#93
post #70

Again a buffer overflow in image decoding, that sounds similar to the one from 2021 [1]. That one was wild, building a CPU out of primitives offered by an arcane image compression format embedded in pdf, to be able to do enough arithmetic to further escalate to arbitrary code execution! [1]: https://googleprojectzero.blogspot.com/2021/12/a-deep-dive-i...

And a much older bug with TIF rendering in iOS 4 used by jailbreakme.com back in the day. It was wonderful pressing a button in Safari and suddenly seeing my iPod touch reboot with Cydia installed.

I would describe a one click rootkit as terrifying as opposed to wonderful.

Re: NSO group iPhone zero-click, zero-day exploit captured in the wild

#94

Earlier quoted context omitted.

>no wonder China is banning government officials from using their devices. Do you actually think security is the reason they are being banned? I think the reasons are far more political than technical.

Technology is political.

Hard truth for people to hear, here. So many insist that all technology is neutral. It's really satisfying to watch the super "enlightened/rational/logical" crowd react emotionally though.

Re: NSO group iPhone zero-click, zero-day exploit captured in the wild

#95

Earlier quoted context omitted.

And a much older bug with TIF rendering in iOS 4 used by jailbreakme.com back in the day. It was wonderful pressing a button in Safari and suddenly seeing my iPod touch reboot with Cydia installed.

I would describe a one click rootkit as terrifying as opposed to wonderful.

If it makes you feel better the click was actually unnecessary theater.

Re: NSO group iPhone zero-click, zero-day exploit captured in the wild

#96

Earlier quoted context omitted.

Some of the problems with iMessage have to do with the fact that it's integrated with the system SMS app. It seems that there are a large number of legacy requirements in the GSM spec that require the Messages app to be privileged in some way, especially with regards to automatic processing of data received. There have been plenty of iMessage or Messages related vulnerabilities. I do wish there was a way to turn off…

Apple's architectural fix here is to move file parsing and other risky operations into proper sandbox harnesses, and to tighten these harnesses year after year. This is the path that WebKit has followed, and the sandbox for the WebKit JIT is incredibly hard to break through these days

Also the path that the Messages app is taking https://googleprojectzero.blogspot.com/2021/01/a-look-at-ime...

Re: NSO group iPhone zero-click, zero-day exploit captured in the wild

#97

[flagged]

I don't think the EU is that much concerned about E-waste. If they were, they would not waste their time with chargers and instead focus on appliances and cars.

These things are not mutually exclusive, iirc they are doing appliances & cars, it's just that phones are often highlighted & batteries are usually the first thing that fails and can be easily replaced in all cases die to how build electronics. Charger standardization was in the pipeline for about a decade so not exactly a priority it being only passed now.

Re: NSO group iPhone zero-click, zero-day exploit captured in the wild

#98

[flagged]

I don't think the EU is that much concerned about E-waste. If they were, they would not waste their time with chargers and instead focus on appliances and cars.

It’s like different people can work on different legislations in parallel, you know?

Re: NSO group iPhone zero-click, zero-day exploit captured in the wild

#99
post #38

Earlier quoted context omitted.

Please... Androids no better. At least Apple will have it patched within the year of discovery. Can't say the same for other Android vendors.

Android is moving away from C and towards more secure languages. From one of their recent blog posts, the majority of code written for android is now in memory safe languages.

Is the programming language likely the issue here?

Re: NSO group iPhone zero-click, zero-day exploit captured in the wild

#100
post #38

Earlier quoted context omitted.

Please... Androids no better. At least Apple will have it patched within the year of discovery. Can't say the same for other Android vendors.

Android is moving away from C and towards more secure languages. From one of their recent blog posts, the majority of code written for android is now in memory safe languages.

Apple also has memory-safer languages it is moving to:

Swift: A memory-safer systems programming language: https://www.swift.org

Firebloom: A memory-safer C variant: https://support.apple.com/en-il/guide/security/sec30d8d9ec1/...

Not sure what the answer is for existing memory-unsafe code.

Post reply on HN