Apple A12 and A13 Hit by Unfixable BootROM Flaw

If you own an iPhone XS, XR, 11, or any device packing an A12 or A13 chip, maybe it’s time to sit down. Apple, the company that wraps its security reputation around terms like “impenetrable” and “device integrity,” just had that fortress gate kicked open. The latest culprit? A hardware exploit called “usbliter8” that leaves millions of iPhones permanently vulnerable. And let’s be honest. This isn’t just some routine security hiccup. You can’t install a patch. You can’t fix this with a hasty overnight update. It’s a hardware bug burned deep into the chip, and your only real option is to buy a new phone. Cozy, right?

BootROM: The Achille's Heel Apple Can't Cover

This all comes down to BootROM, or as Apple likes to call it, SecureROM. It’s the first code your phone runs the second you hit the power button—a little embedded puppet master that checks if the operating system is kosher before letting things proceed. Apple loves touting this as their "secure foundation." Too bad that once a mistake seeps into this slice of silicon, there’s absolutely no erasing it. No magical update, no recall, not even Apple’s legendary PR machine can handwave this away.

The infamous “checkm8” exploit of 2019 shook things up for older iPhone users but drew a comforting line in the sand: any phone newer than the iPhone X was allegedly safe. Today, usbliter8 washes that line away, dragging that sense of security to the grave for a whole new wave of Apple customers. This isn’t just academic: we’re talking iPhone XS, XR, 11s, SE (2nd gen), a chunk of iPads, even Apple Watches and Studio Display. The list really hammers it home—if you thought your three-year-old device was invincible, think harder.

How “usbliter8” Works: Because There’s Always Another Crack

Let’s boil this down. When your iPhone starts up, its USB controller is supposed to behave, storing incoming packets in neatly fenced-off memory. But the usbliter8 exploit, revealed by security researchers at Paradigm Shift, found they could send a series of microscopic packets and trick the controller into scribbling data where it’s not supposed to go. This isn’t some lazy coding mistake—this is a hardware brain fart, embedded so deep you’d need a sledgehammer to fix it.

It gets better. On A12 chip devices, hijacking the boot process was straightforward—an amateur hour for seasoned reverse engineers. Apple, never one to ignore a fire, tried to do damage control with the A13, rolling out Pointer Authentication Codes (PAC) to catch suspicious memory shenanigans. It slowed things, but didn’t stop them. The researchers had to juggle heaps of memory tricks, but they still danced around Apple’s compensations and took full control. The takeaway? Even when Apple reacts, hackers adapt. Fast.

The Fallout: Can This Be Worse? Of Course

Once an attacker gets their foot in the BootROM door, they’re not just peeking around—they’re rearranging the furniture. The usbliter8 exploit makes it possible to run unsigned software, skip critical verification checks, and generally do whatever your paranoid imagination can conjure up. The attack isn’t even subtle. Compromised devices get their USB serial number branded with “PWND”—a little hacker graffiti marking your device as fair game, a nod to the old checkm8 days.

Apple’s Secure Enclave—the biometric vault that’s supposed to guard your passwords and thumbprints—remains officially untouched, for now. But, and this is key, breaking into BootROM gives attackers a pass to try novel (and probably nastier) tricks against Secure Enclave data. It’s like leaving your front door open and praying no one notices the valuables inside.

If You’re Affected, Here’s the Inevitable Advice

So is there a fix coming? Lower your hopes. Paradigm Shift gave Apple plenty of warning, but you can’t update soldered silicon. Apple will huff and puff, but they can’t patch BootROM bugs with software. For the unlucky millions clutching A12 and A13 hardware, the official guidance is painfully simple: upgrade your device. Toss your still-functional gadget, buy something new, and refill Apple’s cash reserves.

  • iPhone XS, XS Max, XR
  • iPhone 11, 11 Pro, 11 Pro Max
  • Second-generation iPhone SE
  • iPad Air 3, iPad mini 5, iPad 8
  • Apple Watch Series 4, Series 5
  • HomePod mini, Studio Display

All now stuck with a doorstop-level vulnerability. Only newer chips with Device Address Resolution Table (DART)—A14 and up—escape unscathed, because Apple finally decided to build the walls a little higher.

Security Theater, or the Cost of Convenience?

It gets tiring, doesn’t it? Every year, tech giants promise ever-stronger bulwarks, and every year someone finds a new crack in the façade. Hardware is especially ugly—the stakes are higher, and the responses are slower. Apple will toss out security updates, but that won’t stop a BootROM bug. Most users won’t notice, or won’t care. But for anyone storing anything more sensitive than cat photos, the news should sting.

The reality: you can’t trust even the most “proven” secure hardware as long as it’s designed by humans with schedules, shareholders, and deadlines. The usbliter8 exploit is a reminder that sometimes, your only choice is to watch for the next Apple launch event and grimly accept the hardware upgrade cycle if you want to stay truly secure.

Or don’t. Just know what you’re risking every time you plug in your compromised iPhone. The ball’s in your court—along with an expensive, unfixable vulnerability you never asked for.

Suggested readings ...