10 ms·
A Look at iMessage in iOS 14
- kccqzy 6y agoThis is actually pretty old news (10+ years old) but it still amazes me to find iOS and macOS sandboxing rules are written in a dialect of Scheme.
- danpalmer 6y agoInteresting! Is it actually a dialect of Scheme or just a LISP syntax custom language? s-expressions are a fairly nice way to create small custom rules languages or configuration languages as they are very easy to parse.
- 1f60c 6y agoMe too! I wonder why that is? I suspect that they wanted to use conditional expressions or something without having to use a "real" programming language with loops or I/O, which risks freezing the interpreter and leaking data.
- messe 6y agoIt's actually a DSL written in scheme that is then used to generate the sandboxing rules, so loops aren't possible. I had the chance to speak with the guys working on it about a year ago. macOS security is pretty neat stuff.
- jes 6y agoI vaguely remember that some settings / control-panel-thingy was written in Scheme on Windows. That was at least 20 years ago, though, so it’s probably gone by now.
- TheKarateKid 6y agoThere are components in Windows that still exist from the NT days, so I wouldn't be surprised if some of these were still there.
- withinboredom 6y agoDid I read this right and see that the exponential back off by launchd would basically cause a DOS for the recipient?
- tedunangst 6y agoBetter than the alternative.
- Thorrez 6y agoWell the attacker could probably DOS the victim anyway by rapidly sending crashing messages. The update just means the attacker only has to send the message every 20 minutes.
- remus 6y agoThat caught my eye too. I guess you would need a way of reliably being able to crash the service but that seems like a relatively low bar. Presumably the impact would also depend on how much work the service does.
- saagarjha 6y agoThe attacker in this situation already has the ability to deny service to the recipient, except they’ve also had the ability to utilize the crashes as an ASLR oracle too. The backoff attempts to prevent this from being possible.
- saagarjha 6y ago> Historically, ASLR on Apple’s platforms had one architectural weakness: the shared cache region, containing most of the system libraries in a single prelinked blob, was only randomized per boot, and so would stay at the same address across all processes. Historically ASLR on Apple’s platforms has had many weaknesses, mostly stemming from poor randomization across many different subsystems :P What I’m also really curious to know is what the performance implications will be of isa PAC…
- pjmlp 6y agoEven if it turns out to be a bit slower, it is the pursuit of speed at the expense of bounds checking that has brought us here, although other ill fated OSes proved that it didn't had to be that way.
- pjmlp 6y ago> The bug was fixed in iOS 14, for example due to the rewrite of large parts of the iMessage processing pipeline in Swift One of the key points.
- saagarjha 6y agoThey’re not out of the woods yet: > However, it is worth noting that while the high level control flow logic is written in Swift, some of the parsing steps still involve the existing ObjectiveC or C implementations. For example, XML is being parsed by libxml, and the NSKeyedArchiver payloads by the ObjectiveC implementation of NSKeyedUnarchiver.
- pjmlp 6y agoAgreed, it is still a first step. rantmode=on While I complain about how constrained NDK happens to be, I imagine that is exactly Google's goal, to force everyone to write as little C and C++ code as possible. Microsoft seems to be the worst case in this regard, despite the whole security talk, WinDev is pretty much doubling down on C and C++. I find ironic that Azure Sphere sells security, yet only supports C on their SDK. rantmode=off My experience with security advocacy, is that only works with seeing is believing. So the initial Swift rewrite might also be to prove a point to the team, while libxml and NSKeyedArchiver will eventually come down the roadmap.
- mikevm 6y ago> Microsoft seems to be the worst case in this regard, despite the whole security talk, WinDev is pretty much doubling down on C and C++. From what I understand, MS is gradually moving away from C/C++: https://thenewstack.io/microsoft-rust-is-the-industrys-best-chance-at-safe-systems-programming/ https://thenewstack.io/microsoft-rust-is-the-industrys-best-...
- pjmlp 6y agoVery very gradually, Check the praise for C and C++ over here, https://microsoft.github.io/microsoft-ui-xaml/ https://microsoft.github.io/microsoft-ui-xaml/ https://techcommunity.microsoft.com/t5/internet-of-things/developing-secure-coding-in-azure-sphere/ba-p/1796510 https://techcommunity.microsoft.com/t5/internet-of-things/de... Or how XNA was killed in name of DirectXTK. Meanwhile the MonoGame, Unity, WaveEngine, and for IoT, Meadow (what Sphere should have been) efforts are all driven by third parties. Joe Duffy mentions on his RustConf talk that even with Midori proving it was capable to handle production loads (it even powered parts of Bing for a while), it was a no go for Windows team. Apparently the culture change in WindowsDev will take a couple of generations.
- ondrek 6y agoThe original article from December: > In July and August 2020, government operatives used NSO Group’s Pegasus spyware to hack 36 personal phones belonging to journalists, producers, anchors, and executives at Al Jazeera. The personal phone of a journalist at London-based Al Araby TV was also hacked. > The phones were compromised using an exploit chain that we call KISMET, which appears to involve an invisible zero-click exploit in iMessage. In July 2020, KISMET was a zero-day against at least iOS 13.5.1 and could hack Apple’s then-latest iPhone 11.
- Krasnol 6y agoSo can one buy standings on the HN overview now or how is it that those Apple news are always right on top? This thing has only 190 upvotes and ridiculous 12 comments atm and is on top.
- Krasnol 6y agoThe only thing faster than an Apple post to the top, goes a comment questioning this weird pattern. -1 in one minute in a 12 comment post. Not bad
- deleted 6y ago[deleted]
- dang 6y agoPlease don't post like this. You're breaking the site guidelines badly. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- piva00 6y agoI'm no admin but wanted to ask for you to refrain commenting like this, it's probably against the site's guidelines and brings nothing to the discussion. Per the guidelines: "Please don't comment about the voting on comments. It never does any good, and it makes boring reading."
- eecc 6y agoIt’s a conspiracy of course. Now go buy your Apple stock, sit back and enjoy the profit /s
- robin_reala 6y agoHN upvotes what HN wants to see. Apple is one of the biggest companies in the world with products that a large majority of HN commenters use, and this blog post is in-depth technical praise / validation written by a representative from one of their biggest competitors. It feels like classic top-post material to me.
- 6y ago
- snoshy 6y agoThis is the equivalent of a negative research result that looked into whether there's anything more to explore here to produce the really juicy result like a true compromise, but instead shows that there's nothing that a set of highly qualified researchers can prove, at least. I applaud more of this, although it is not an infrequent practice among the top security engineers, I feel it sets a precedent for research broadly. Nothing to be found here as far as we know, is still a result that deserves publishing. Let's make it more of the norm.
- rat9988 6y agoI feel like you are claiming researchers do not do it.
- ksml 6y agoI read it as GP arguing we don't do enough of it.
- rat9988 6y agoMy english may be failing me here, but doesn't > I feel it sets a precedent for research broadly imply it's some sort of first time?
- vulcan01 6y agoGenerally, precedent means first "well-known" time, or first time by a respected person/institution/company. I don't know enough about this field to know if this is the first time Google has published a negative result.
- snoshy 6y agoThis is a fair point to consider. Perhaps my claim was a bit overbroad.
- snoshy 6y ago
- opendysphoria 6y agohttps://twitter.com/quasiprobable/status/1355006188543328260 https://twitter.com/quasiprobable/status/1355006188543328260
- deleted 6y ago[deleted]
- mensetmanusman 6y agoAt some point we would expect that the world would experience a zero day worm that works its way through the entire iMessage ecosystem, because a majority of the users are all on the latest version... I wonder when that will happen
- spzb 6y agoI've read that three times and I still can't parse it. Why would being on the latest version make a zero day worm more likely?
- dewey 6y agoI've read it as a way of saying that the fragmentation of iOS versions is way lower than on Android. So if a "latest iOS"-only zero day would've been found it would affect a lot of users as they tend to update quickly.
- bsdetector 6y agoComplicated to exploit bugs often rely on specific code and data being in particular places or even the number of cycles a code block takes so even if the same bug had existed for years you might have to write a separate exploit for each version. And make a version check if failed attempt will crash the software or you only get one attempt. Sometimes the hardest part is finding out what version of exploit to use and that may even have to be done manually.
- mensetmanusman 6y agoSorry for the confusion, it seems that in a software monoculture, where everyone has the same iOS version, a zero-day (which in theory will almost certainly always exist in complex system) would travel more effectively than in a system with lots of OS versions. E.g. a zero-click zero-day exploit that spreads through a zero-click iMessage message could travel the world in a few seconds.
- ogre_codes 6y agoThe days of internet massive worms are behind us. Or at least mostly. Security is vastly better than it used to be and good zero day exploits are guarded jealously. Making a big worm is a quick way to expose a zero day. The people who have access to these zero day exploits keep them tight for targeted attacks where they are less likely to be discovered.
- grandinj 6y agoFinally, we are seeing more applications pushing chunks of themselves into sandboxed sub-processes. Now if only there was a nice open-source, cross-platform way to do this..... hint..... hint...... :-)
- saagarjha 6y agoPerhaps I’m too dense to get the hint?
- grandinj 6y agoWhat I mean is, it would be really nice if someone would build such a toolkit - I know the code exists inside things like Chrome and Firefox, but I'm not aware of any standalone libraries that make it easy to (a) create a sandboxed child process with some code inside it (b) talk to that sandboxed child process (e.g. Firefox and Chrome both have IPC libraries) (c) handle the resulting crashes nicely, restarting child process when necessary
- saagarjha 6y agoSadly not possible on iOS. Even on macOS, creating a good sandbox profile is non-trivial (and technically unsupported by Apple).
- HHad3 6y agoOpen source aside, it would be great if any developer could do this on iOS. Unfortunately -- in contrast to macOS -- Apple keeps the XPC API on iOS private, so that it is impossible for "normal" app developers to properly sandbox the more critical and exposed parts of their application. Only Apple can provide the described security for their messenger, but other messengers which face similar challenges (rendering untrusted content) cannot protect themselves.
- my123 6y agoApple doesn't allow subprocesses for 3rd-party apps on iOS generally as far as I know.
- nonane 6y agoDoes anyone know if there's a cross platform library that offers similar services like Blastdoor and a sandbox for apps to run sensitive code in?
- thedg 6y agoWoah