Brussels, Belgium – European cybersecurity firm Paradigm Shift has publicly detailed a new hardware-level BootROM exploit, dubbed "Usbliter8," that compromises the SecureROM component in millions of Apple devices built on A12 and A13 Bionic chips. The flaw affects widely used products such as the iPhone XS, iPhone XR, the iPhone 11 series, and the Apple Watch Series 4 and Series 5, all released between 2018 and 2019 and still in active use. Usbliter8 targets Apple’s SecureROM, the immutable code that runs first during device startup and anchors the company’s secure boot chain, meaning the underlying vulnerability cannot be corrected through standard iOS or watchOS software updates because the affected code is permanently embedded in the system-on-chip hardware. Paradigm Shift’s technical disclosure explains that the exploit chains a bug in the device’s USB controller with a specific firmware configuration weakness to gain low-level control. To execute the attack, an operator must have physical access to the device and connect a specialized hardware interface, such as a Raspberry Pi Pico 2 or similar microcontroller board, to the Lightning or USB-C port. The interface sends carefully crafted USB setup packets that trigger an out-of-bounds write in memory, allowing the attacker to overwrite critical data in the processor’s registers. This sequence gives the attacker a reliable path to undermine the secure boot process on vulnerable hardware, while remaining dependent on direct, hands-on access to each targeted device.
Prepared by Jonathan Pierce and reviewed by editorial team.
If you own an iPhone XS, XR, 11, or Apple Watch Series 4 or 5, your device could be vulnerable. The exploit requires physical access to your device, so keep it secure. Check for updates from Apple regularly.
This flaw can't be fixed with a simple software update. It's a hardware issue. But remember, an attacker needs hands-on access to your device. Worth forwarding if you know someone with these Apple models.
Not specified in source.
Not specified in source.
No left-leaning sources found for this story.
No right-leaning sources found for this story.
Comments