Top
Best
New

Posted by pavel_lishin 18 hours ago

Today, we hacked what we'd set out to hack: the iPhone(blog.calif.io)
884 points | 577 commentspage 4
post_break 16 hours ago|
Please let this be real. I need my 17 Pro to be jailbroken. I may keep my 13 Mini if it works for it too. This will be bliss.
nsxwolf 18 hours ago||
What are these videos actually demonstrating?
jeroenhd 17 hours ago||
A couple of PDF exploits from iMessage and Signal leading to code execution, and an app that roots the phone. Also, they seem to have managed to make their malware survive a reboot, which is difficult. That's another reason why automatic reboots are considered a security feature: exploits leaving malware in-memory are a lot easier to build than malware that survives a full reboot, passing all stages of signature checks and validation.
ks2048 17 hours ago|||
Yes, why don't they just say it instead of posting videos. Opening a sinister PDF in iOS can give them access to what exactly? anything/everything? What iOS versions or devices, etc?
sunaookami 15 hours ago|||
Marketing by security researchers and companies has gotten unbearable. They only want their name out there and not actually make devices more secure.
cryptbe 12 hours ago|||
We disclosed most bugs to Apple, and are going to disclose the rest. We've disclosed probably close to 100 bugs to Apple in the past 6 months.

We've also been working with closely with the Signal Foundation to help them reduce the attack surface.

It's not true that we don't want to make devices more secure. We do and it's why we do this research.

We also do want our name out there because we're having a lot of fun and want to share that with our friends and the rest of the world.

r_lee 12 hours ago|||
how are they supposed to get paid?
cryptbe 12 hours ago|||
Check out https://calif.io/research/the-great-glyph-grift, which shows one could go wrong with PDF in iOS.

We're gonna publish more in the coming weeks. Writing these blog posts take time, and we've been busy with another PHP thing.

r_lee 12 hours ago||
> with another PHP thing.

oh man...

dt3ft 16 hours ago||
Rooting, pretty much. Aka, executing code which shows their flying logo, but could also be exfiltrating data without displaying anything.
rzimring 15 hours ago||
This post gave me flashbacks to jailbreak era w/ Cydia. It's interesting to think that a lot of the those old plugins and tweaks have basically become standard supported features of the iOS now (SBSettings, Activator, WinterBoard, Zephyr, ...).
SoKamil 18 hours ago||
Stay on 27.0 or upgrade to 27.0.1?
cardboard9926 17 hours ago||
How did they bypass MTE? Wasn't it suppose to make such exploits basically impossible?
Panino 17 hours ago|
We don't know if Calif bypassed MIE.

When they hacked the M5 (one week after release!), they used a data-only attack, which is outside the scope of MIE. That could be the case here, or something else entirely. We don't know.

https://news.ycombinator.com/item?id=48139219

cromka 18 hours ago||
Someone correct me please if I’m wrong but is this because iOS doesn’t sandbox their processes? I think I read Safari in particular doesn’t, but wonder if this is system-wide issue.

The more of this stuff we see, the more people will start using GrapheneOS, I guess.

Also wonder why they choose to publish and not cash-in the Apple bounty..

odo1242 17 hours ago|
iOS does sandbox their processes really well, that's why this hack was as difficult as it was. The Safari thing you're talking about is JIT - iOS disables all runtime code generation across the system except in Safari (for JavaScript), but this is a completely separate thing from sandboxing.
cromka 15 hours ago||
Actually, no, I now remember this was about iMessage specifically and how it isn't completely isolated/runs as system service or sth? Or about the renderer?

Which would make sense because these attacks seem to exploit the same weakness.

odo1242 13 hours ago||
iMessage's attachment renderer is also sandboxed, actually. You might be talking about this vulnerability: https://projectzero.google/2021/12/a-deep-dive-into-nso-zero..., but the second half of the vulnerability exploit chain was finding a way out of the CoreGraphics (Apple's image rendering library) sandbox to hack the rest of the system.
cromka 12 hours ago||
Yes, I think that was it, thanks!
josh2600 14 hours ago||
Is this day0 or did apple and signal get notified?
dangoodmanUT 17 hours ago||
so i see we're still going with the apocalypse today too
smasher164 17 hours ago|
why do we see pdf viewer exploits on ios when we have sandboxing mechanisms nowadays like wasm? Or is this exploit accounting for the sandbox breakage?
More comments...