4 ms·
Is this an issue of complexity or lack of isolation? More isolation means more complexity, but at the same time, this issue should crash the iMessage app itself
by viraptor 7y ago
Is this an issue of complexity or lack of isolation? More isolation means more complexity, but at the same time, this issue should crash the iMessage app itself, not the whole system. The fact that springboard even knows about iMessage structure is crazy...
- olliej 7y agoright? ignoring the issue of invalid assumptions in iMessage taking content from the network (though at least it's objective-c so it's a "DoS" rather than RCE). The problem here seems to be that the code handling the incoming message is inexplicably running inside springboard rather than a separate process. :-/
- saagarjha 7y ago> invalid assumptions in iMessage taking content from the network (though at least it's objective-c so it's a "DoS" rather than RCE) In this case. In general, however, Objective-C can often fall victim to attacks where poorly validated attacker data ends up causing RCE: see the entire reason for the existence of NSSecureCoding.
- kirb 7y agoI’ve somewhat researched iMessage handling on iOS for a jailbreak tweak called TypeStatus, and I find this bug odd. In iOS 7, SpringBoard was restricted at the sandbox (kernel) level from any access to the Messages database. I had to adapt my code to instead run inside imagent, which is responsible for keeping a push socket open with iMessage among other Messages housekeeping things (this also exists on macOS). There was a trend since iOS 6 to move backend/non-UI responsibilities away from SpringBoard. But in iOS 11 or 12 or so, more responsibilities started creeping back into SpringBoard. Maybe because of performance or memory consumption concerns, maybe it’s laziness avoiding having to set up a new daemon with appropriate dependencies and sandbox profile when the code can easily be plopped into SpringBoard, it’s not clear. As Natalie says in the report, on macOS this bug only causes DoS on a daemon. Worst case, iMessage stops working and your battery dies quicker. Being totally locked out of the device because SpringBoard is “boot looping” due to an existing fail-safe being excluded from the design seems awful. On the subject, my Android phone stopped even presenting a keyboard on the lock screen or anywhere else, because the default keyboard is Gboard, and Gboard relies on Play Services, which was crashing inside Gboard. Like this iOS bug, the only known solution is to wipe the device and start over. At least I was still able to get into the device by connecting a USB keyboard. Sucks to know most would have no idea how to diagnose such an issue though, needlessly wiping their photos and all.
- userbinator 7y agoComplexity. You don't really need isolation if the code is so simple as to obviously contain no bugs (instead of containing no obvious bugs.) Instead, we have a whole industry built upon encouraging the creation of things as complex as possible, and working around the problems caused by that by adding even more complexity, mainly because it means people have more to do. http://countercomplex.blogspot.com/2014/08/the-resource-leak-bug-of-our.html http://countercomplex.blogspot.com/2014/08/the-resource-leak... (No, downvotes from the complexity-brigade are not going to make me change my mind either.)
- viraptor 7y agoI think you could achieve low complexity at the time of early feature phones. If you get a web browser and loadable untrusted binaries in the system, you've lost this battle. There is no way to make those "obviously contain no bugs". So you're kind of right, we wouldn't need isolation... if not for the fact modern mobiles exist. But even then - people are creative. Software may be obviously bug free, hardware may be obviously bug free... then someone comes up with rowhammer and you're owned by pure physics. I'm not sure "obviously bug free" even exists.
- icebraining 7y ago> No, downvotes from the complexity-brigade are not going to make me change my mind either. What would?
- saagarjha 7y agoSpringboard itself doesn't, but it loads a framework into itself that does; commenters here have suggested this is because it needs to render notifications: https://news.ycombinator.com/item?id=20380588 https://news.ycombinator.com/item?id=20380588