Apple Facing Class Action Lawsuit Over 'Error 53' iPhone 6 Bricking

iphone6s-gold-select-2015Seattle-based law firm Pfau Cochran Vertetis Amala (PCVA) today followed through with plans to bring a class action lawsuit against Apple over the "Error 53" controversy that made headlines last week.

"Error 53" is the error code that some iPhone 6 owners have received after third-party repairs that affect Touch ID were made to their iPhones, rendering the devices unusable. As explained by iFixit, repairs made by third-party services using components not sourced from the original device cause the iPhone to fail a Touch ID validation check because the mismatched parts are unable to properly sync. Parts that can impact Touch ID include the screen, flex cable, and Home button.

When this Touch ID validation check fails during an iOS update or restore, Apple disables the iPhone, effectively "bricking" it in an effort to protect Touch ID and the related Secure Enclave that stores customer fingerprint information. Apple says that without the validation check, a malicious Touch ID sensor could be used to gain access to the Secure Enclave.

PCVA attorney Darrell Cochran, who is leading the Error 53 lawsuit, claims that Apple's security argument is invalid because affected iPhones often work fine for several months following repairs as the validation check only occurs when downloading a new version of iOS. He also cites Apple's failure to give a warning about the consequence of an update as an issue that will be featured in the lawsuit.

"No materials we've seen from Apple ever show a disclosure that your phone would self-destruct if you download new software onto a phone," Cochran said. "If Apple wants to kill your phone under any set of circumstances and for any reason, it has to make it crystal clear to its customers before the damage is done."

Compounding the problem, according to Cochran, is how disagreeable Apple's reaction to the problem has been. "The error code 53 signals the death of the phone, and Apple's response has been to say 'you have no options; it's not covered under warranty, and you have to buy a new phone.'"

PCVA is aiming to get affected iPhone customers new, working devices to "provide immediate relief" to consumers. It is also seeking upwards of $5 million in damages and an update to eliminate the repair restrictions. PCVA is asking customers who have been impacted by Error 53 to get in touch.

Aside from explaining the reasoning behind the Error 53 message and its consequences, Apple has remained quiet about the controversy. MacRumors has, however, heard from a retail source that certain Apple Stores have received the go ahead from Apple to replace third-party screens and other components to resolve the issue. It is not yet clear if this replacement policy will be extended to all Apple Stores or if Apple will make an official comment on the situation.

Related Forum: iPhone

Top Rated Comments

Markoth Avatar
78 months ago
So... They made third-party repairs, which annulled their warranty, and bricked their phone and now they're suing? Why does Apple owe them anything, exactly? Didn't they agree to Apple's terms when they purchased the device?
Score: 42 Votes (Like | Disagree)
Muzzakus Avatar
78 months ago
Totally justified lawsuit. There is absolutely no reason to brick the phone for an optional feature such as touchid. Invalidate the fingerprints and allow the user to continue using the phone via the regular pin.
Score: 34 Votes (Like | Disagree)
springsup Avatar
78 months ago
There is so much misinformation about this, I'm going to repost the technical explanation I gave in the other thread:

The API hides a lot of the implementation details, so most developers won't know how it really works, but Apple document it in their iOS Security Guide (PDF) ('https://www.apple.com/business/docs/iOS_Security_Guide.pdf').

When you boot your iPhone up, the filesystem is encrypted. It's just full of meaningless junk; you can't use the phone. Once you enter your passcode for the first time, the system reads the filesystem key (which itself is stored encrypted by your passcode), and tries to decrypt it. If your passcode is correct, it will end up with the correct filesystem key, and it can unlock your iPhone's hard drive and read useful data from it. This filesystem key is called "NSFileProtectionComplete".

(NSFileProtectionComplete): The class key is protected with a key derived from the user passcode and the device UID.
... when a passcode is entered, the NSFileProtectionComplete key is loaded from the system keybag and unwrapped.
IMPORTANT: At this point your phone is unlocked. That is all there is to it. This filesystem key gets placed in the Secure Enclave so your iPhone can read/write from its hard drive. We haven't used TouchID or fingerprints so far, just a passcode. This is why you always need to give your passcode after a restart.

So how does TouchID work, exactly?

Let's look at what happens when you lock the phone, and how it's different between TouchID and non-TouchID:

If Touch ID is turned off, when a device locks, the keys for Data Protection class Complete, which are held in the Secure Enclave, are discarded. The files and keychain items in that class are inaccessible until the user unlocks the device by entering his or her passcode.

With Touch ID turned on, the keys are not discarded when the device locks; instead, they’re wrapped with a key that is given to the Touch ID subsystem inside the Secure Enclave. When a user attempts to unlock the device, if Touch ID recognizes the user’s fingerprint, it provides the key for unwrapping the Data Protection keys, and the device is unlocked.
So basically if you have TouchID disabled (passcode only), this key gets thrown away and you need to enter the passcode again next time you unlock. It's the exact same process as you go through on first-boot.

What Apple is saying here is that TouchID just holds on to the key which you already obtained via your passcode for a while (48 hours if the device stays on). But is TouchID really completely optional? Let's ask Apple:

When Touch ID scans and recognizes an enrolled fingerprint, the device unlocks without asking for the device passcode. The passcode can always be used instead of Touch ID
Okay, I guess that settles it.

What about other stuff like iTunes/ApplePay purchases? How does that work with TouchID?

Touch ID can also be configured to approve purchases from the iTunes Store, the
App Store, and the iBooks Store, so users don’t have to enter an Apple ID password. When they choose to authorize a purchase, authentication tokens are exchanged between the device and the store. The token and cryptographic nonce are held in the Secure Enclave. The nonce is signed with a Secure Enclave key shared by all devices and the iTunes Store.
So when you enter your iTunes Store password the first time after a reboot, your device gets a temporary token to use for purchases, stores it in the Secure Enclave, and guards it behind TouchID. Again, it's totally optional; just a shortcut for entering your password.

The same applies to Apple Pay:

The Secure Element will only allow a payment to be made after it receives authorization from the Secure Enclave, confirming the user has authenticated with Touch ID or the device passcode. Touch ID is the default method if available but the passcode can be used at any time instead of Touch ID. A passcode is automatically offered after three unsuccessful attempts to match a fingerprint and after five unsuccessful attempts, the passcode is required. A passcode is also required when Touch ID is not configured or not enabled for Apple Pay.
Man, Apple is really going to regret writing this document...

So yeah, in conclusion:

1. it is totally technically possible to rip the TouchID sensor out of your phone and still be able to unlock it (assuming you have the passcode).
2. TouchID does not seem to be essential for any single feature of the device; it is only ever a shortcut for entering the passwords you have already recently entered in to the phone.
3. It's really weird that Apple only check the TouchID sensor's integrity when they update the OS. Surely they should check that on every boot?

So what did Apple do wrong?

1. Apple should have communicated better (not when performing the update, but when buying the device!) that the TouchID sensor can only be replaced by an authorised technician.
2. If the TouchID sensor is compromised, they should fall-back to the passcode. As I said, the passcode is the only thing you really need to unlock the device.

Law firms? I just did all of your investigation work for you. Feel free to cut me a cheque.

EDIT: Rewritten for greater clarity for non-technical folks.
EDIT2: My personal feeling is that this is a bug -- I mean, what if the legit sensor developed a hardware fault? You don't want the machine to just lock all access. I think Apple did intend to fall-back to the passcode if the TouchID sensor, but unfortunately this is a catastrophic bug: even if Apple fix it, once you're locked out of the phone you can't update to get the fix. They should release a software update ASAP and repair any affected phones for free.
Score: 34 Votes (Like | Disagree)
ToroidalZeus Avatar
78 months ago
Seems like they have legit case.

So... They made third-party repairs, which annulled their warranty, and bricked their phone and now they're suing? Why does Apple owe them anything, exactly? Didn't they agree to Apple's terms when they purchased the device?
There is a lot of misinformation on this subject. The "brick" happens when someone replaces the TouchID sensor--with a GENUINE OR 3rd party part. Apple is most likely within their right to disable TouchID when they detect a mismatched sensor as it's a security risk. However bricking the device and not giving any warning is probably going too far.
Score: 30 Votes (Like | Disagree)
lampwins Avatar
78 months ago
It amazes me how little people actually care about their security (and do not confuse security with privacy here). Apple is trying to protect its users, but they are too stupid to realize.

But on the other hand, Availability is a part of the CIA triad so bricking the phone does violate this premise.

However, Apple is doing this because a piece of hardware inserted between the Touch-ID Sensor and the Secure Enclave could in theory either intercept scans or access the enclave.

They are doing this to protect you, not as a "screw you for trying to fix your own phone." People will always see what they want to see though, I suppose.
Score: 29 Votes (Like | Disagree)
goobot Avatar
78 months ago
I agree that their Touch ID should be disabled, but is there some reason that's not possible?

If they got a message saying "Touch ID disabled" I'd say these people have no case.

But as it is, isn't this like making your iMac refuse to boot because you broke the DVD drive?
It's more like a car not starting because you tried a cheap knockoff key.
Score: 21 Votes (Like | Disagree)

Popular Stories

airpodsinear 1

AirPods Save Woman's Life With Feature Everyone Should Know

Friday January 21, 2022 2:13 am PST by
Apple's AirPods have been credited with saving a woman's life after a potentially fatal fall, People reports. When a 60-year-old florist in New Jersey tripped and hit her head in her studio, she lost consciousness and awoke heavily bleeding. With nobody around to call for help, she realized she had her AirPods in, and used a "Hey Siri" command to call 911. An operator was able to stay on the ...
maxresdefault

Review: M1 Max MacBook Pro After Three Months

Wednesday January 19, 2022 11:30 am PST by
It's now been a few months since the M1 Pro and M1 Max MacBook Pro models launched in October, and MacRumors video editor Dan Barbera has been using one of the new machines since they debuted. Over on the MacRumors YouTube channel, Dan has shared a three month review of his MacBook Pro to see how it has held up over time and how it's changed his workflow. Subscribe to the MacRumors YouTube ...
iphone se 2020 top

New iPhone SE Likely to Launch in April Based on Production Timeframe

Wednesday January 19, 2022 6:44 am PST by
Apple suppliers will begin producing display panels for the third-generation iPhone SE this month, with final assembly of the device likely to start in March, according to information shared by display industry consultant Ross Young. Based on this production timeframe, Young believes the third-generation iPhone SE is likely to launch in the second half of April, or perhaps in early May at...
iphone 13 earpods

Apple to Stop Including EarPods With Every iPhone Sold in France From Next Week

Friday January 21, 2022 3:21 am PST by
Apple will no longer include EarPods with every iPhone sold in France, starting on January 24, according to a notice posted by a French carrier (via iGeneration). Apple was previously required to include EarPods in the box with the iPhone due to a French law that required every smartphone sold in the country to come with a "handsfree kit," but the law has now been changed in favor of reducing the ...
Spring 2022 Apple Products Feature

New iPad Air, Macs, and iPhone SE With 5G Likely to Be Announced at Apple Event This Spring

Thursday January 20, 2022 8:32 am PST by
Earlier this week, Bloomberg's Mark Gurman tweeted that Apple "will be holding a spring event" to announce a new iPhone SE and other hardware. In a recent edition of his newsletter, Gurman said the event is likely to occur in March or April. Gurman did not elaborate on what "other hardware" will be announced at Apple's purported spring event, but rumors suggest at least four products are...
peloton tv workout cardio

Apple Floated as Potential Buyer of Peloton

Friday January 21, 2022 6:11 am PST by
Following months of bleak news about Peloton's "precarious state," including the revelation that it has halted production of its bikes and treadmills, Apple is being floated as a potential buyer of Peloton's troubled fitness business. Yesterday, CNBC reported that Peloton will temporarily stop production of its connected fitness products due to a "significant reduction" in consumer demand, a ...
apple watch series 7 aluminum colors yellowbg

Apple Watch Charging Bug Fixed in watchOS 8.4 Release Candidate

Thursday January 20, 2022 4:01 pm PST by
The watchOS 8.4 release candidate that was seeded to developers and beta testers this morning addresses an ongoing bug that could cause some Apple Watch chargers not to work properly with the Apple Watch. Back in December, we reported on a growing number of charging issues that Apple Watch Series 7 owners were facing. Since watchOS 8.3, there have been a number of complaints about...
appleprivacyad cleaned

iOS 15 Patched Security Hole That Potentially Exposed Users' Private Apple ID Information to Third-Party Apps

Thursday January 20, 2022 3:32 am PST by
Apple patched two significant security vulnerabilities when it released iOS 15 that could have potentially exposed users' private Apple ID information and in-app search history to malicious third-party apps and allowed apps to override user Privacy preferences, Apple has revealed in a recent support document update. With most iOS, macOS, tvOS, and watchOS updates, Apple provides a list of...
safari icon blue banner

macOS Monterey 12.2 and iOS 15.3 Release Candidates Fix Safari Bug That Leaks Browsing Activity

Thursday January 20, 2022 1:30 pm PST by
The macOS Monterey 12.2 and iOS 15.3 release candidates that came out today appear to address a Safari bug that could cause your recent browsing history and details about your identity to be leaked to malicious entities. As shared last week by browser fingerprinting service FingerprintJS, there is an issue with the WebKit implementation of the IndexedDB JavaScript API. Any website that uses...