←back to thread

265 points fortran77 | 5 comments | | HN request time: 0.806s | source
Show context
acdha ◴[] No.42189685[source]
Interesting that they’re mentioned as only being exploited on Intel. Has anyone seen whether that’s because the attacker only targeted that platform or is it actually stopped by something like pointer protection?
replies(3): >>42189761 #>>42189809 #>>42189932 #
justinclift ◴[] No.42189809[source]
Doesn't seem to completely line up that they're rushing out iOS updates (ie for phones, etc) for something they're saying they've only confirmed on Intel cpus.

Unless they're assuming it's exploitable on Apple Silicon as well, or are being extra careful just in case.

replies(7): >>42189876 #>>42189883 #>>42190175 #>>42190448 #>>42190733 #>>42190776 #>>42190850 #
1. oddevan ◴[] No.42189883[source]
> Unless they're... being extra careful just in case.

That's where my money is.

replies(2): >>42190127 #>>42190431 #
2. ajross ◴[] No.42190127[source]
Or they just don't know. Full analysis of an exploit usually takes days to weeks. It's possible it's only exploitable on x86, but equally possible that only the x86 version of the payload was discovered in the wild.
replies(1): >>42190542 #
3. ruthmarx ◴[] No.42190431[source]
Why? Putting a lot of stock in Apple's various protections?
4. 486sx33 ◴[] No.42190542[source]
Rosetta2 runs an x86 exploit? Doesn’t explain iOS but still sounds interesting!
replies(1): >>42191707 #
5. ◴[] No.42191707{3}[source]