3 ms·
May 2022, https://dl.acm.org/doi/abs/10.1145/3507657.3528547 https://dl.acm.org/doi/abs/10.1145/3507657.3528547 > On recent iPhones, Bluetooth, Near Field Comm
by walterbell 4y ago
May 2022, https://dl.acm.org/doi/abs/10.1145/3507657.3528547 https://dl.acm.org/doi/abs/10.1145/3507657.3528547
> On recent iPhones, Bluetooth, Near Field Communication (NFC), and Ultra-wideband (UWB) keep running after power off, and all three wireless chips have direct access to the secure element. As a practical example what this means to security, we demonstrate the possibility to load malware onto a Bluetooth chip that is executed while the iPhone is off.
LTE baseband issues, not specific to Apple, https://gist.github.com/adaburrows/fda8711e468858fc5ace98daf2d73148 https://gist.github.com/adaburrows/fda8711e468858fc5ace98daf...
- tptacek 4y agoThe paper lays this out: there are baseband features that use the Secure Element, and talk to it over I2C, because it stores secrets for things like (I guess?) car keys. That doesn't mean those chips can DMA things into and out of the Secure Element. For clarity: the Secure Element is the payment chip in the phone; it's not the SEP, the "Secure Enclave". The Enclave's memory is, in addition, hardware-encrypted. The cellular baseband on an iPhone is an HSIC peripheral.
- walterbell 4y agoDefense in Depth is good (TM). It's still worthwhile to deny malware from foothold on iPhone radios, e.g. an official process to verify baseband integrity and if necessary, restore official firmware without waiting for the next baseband security update.
- tptacek 4y agoI agree, more transparency is good. Baseband transparency would be a good thing. But even more important is a sound architecture. Lots of people believe that 3rd-party firmware running on iPhones can read and write any memory on the phone (and also that "DMA" means "god mode", like it did in 1997). The fact is that Apple (and Google, for its flagship phones) spend a fortune on internal and external design and implementation expertise that all starts from the premise of "code we didn't write is suspicious as fuck" and works back from there to a secure design. There Will Be Bugs! I just hope people recognize that they haven't outguessed Apple and Google simply by noticing that third-party firmware developers ship blobs instead of source repos. It's a hugely interesting space for security development and research, and I wince when I feel like it's getting oversimplified. Which you didn't do! It's just a hobbyhorse.