I managed fine before the T2 chip existed, I will manage fine with a T2 chip that has a vulnerability.
Yes. A reboot fixes it unless the device is still connected. And it’s a device, not just a cable. The cable allows the device to do what it wants to do.I don't understand how this works. Where is the keyloigger installed? Wouldn't a power-off / reboot flush it out?
Tell that same thing to Intel before you start throwing stones only at Apple.And what are we gonna do until then? If this is an unfixable, unpatchable possible exploit, isn't it grounds for a mass product recall?
It doens't so much bypass login as run before the login prompt is shown.Yes. A reboot fixes it unless the device is still connected. And it’s a device, not just a cable. The cable allows the device to do what it wants to do.
Big question: does it bypass password login? If not, it requires this thing to be discretely connected directly to the usb-c on the computer and the owner not noticing. Or if I am missing something?
What repairs other than keyboard/screen? Everything else is soldered into the logic board. Most shops do not have the capability of replacing soldered SSD flash chip.Hopefully this is exactly what this hack accomplishes, is create tools for independent repair shops that will now be able to repair T2 Macs.
But I imagine Apple will find a way to detect that the repairs were done in an "unauthorized way", and blacklist those Macs from running the OS, or getting updates, or brick them alltogether - like they have with iPhones.
Seems like the response could be “if T2 reboots, OS locks up?” So basically have the device kernel panic on T2 reboot?Thanks, watched the video and read the linked article ... so you need a power brick sized special device to initiate this. And I understand that this action actually reboots the T2 chip which seems odd that it can be rebooted while the Mac is running, but so be it.
Will be interesting to see Apple's response ...
Unless you work for the government, probably not.
Tell that same thing to Intel before you start throwing stones only at Apple.
then we should place all of our trust in intel. right? RIGHT?![]()
There’s no such thing as a “secure” chip.
With enough time and effort, everything is hackable.
Sure, but when it's the chip specifically meant for security, it's kind of a "you had one job!" failure.
As if there weren't enough reasons to avoid those models already.The T2 chip causes too many problems already. Our shop sees too many with filevault corruption, or needing to reflash the chip which takes 3-5x even though it states it is successful. I would avoid all the USB-C models as of right now.
The T2 chip causes too many problems already. Our shop sees too many with filevault corruption, or needing to reflash the chip which takes 3-5x even though it states it is successful. I would avoid all the USB-C models as of right now.
Kinda makes the remote work concept difficult to achieve for many people.If they have physical access, it's game over. If they have physical access to a running machine, it's definitely game over. Simple solution to this in the real world: power off the machine before you leave it unattended.
But only if that chip was protected by a T4 chip.Had Apple protected the T2 with a T3, we would not be here today.
Oh for F sake.
After it was reported last week that Apple's T2 Security Chip could be vulnerable to jailbreaking, the team behind the exploit have released an extensive report and demonstration.
![]()
Apple's custom-silicon T2 co-processor is present in newer Macs and handles encrypted storage and secure boot capabilities, as well as several other controller features. It appears that since the chip is based on an Apple A10 processor, it is vulnerable to the same "checkm8" exploit that has been used to jailbreak iOS devices.
The vulnerability allows for the hijacking of the T2's boot process to gain access to the hardware. Normally the T2 chip exits with a fatal error if it is in Device Firmware Update (DFU) mode and it detects a decryption call, but by using another vulnerability developed by team Pangu, it is possible for a hacker to circumvent this check and gain access to the T2 chip.
Once access is gained, the hacker has full root access and kernel execution privileges, although they cannot directly decrypt files stored using FileVault 2 encryption. However, because the T2 chip manages keyboard access, the hacker could inject a keylogger and steal the password used for decryption. It can also bypass the remote Activation Lock used by services such as MDM and Find My. A firmware password does not prevent this since it too requires keyboard access, which requires the T2 chip to run first.
The exploit can be achieved without user interaction and simply requires a modified USB-C cable to be inserted. By creating a specialized device "about the size of a power charger," an attacker can place a T2 chip into DFU mode, run the "checkra1n" exploit, upload a key logger, and capture all keys. macOS can be left unaltered by the jailbreak, but all keys can still be logged on Mac laptops. This is because MacBook keyboards are directly connected to the T2 and passed through to macOS.
A practical demonstration shows checkra1n being run over USB-C from a host device. The targeted Mac simply displays a black screen while the connected computer confirms that the exploit was successful.
These cables function by allowing access to special debug pins within a USB-C port for the CPU and other chips that are usually only used by Apple.
Apple has not fixed the security flaw and it appears to be unpatchable. For security purposes, the T2's SepOS custom operating system is stored directly in the chip's SEPROM, but this also prevents the exploit from being patched by Apple via a software update.
In the meantime, users can protect themselves from the exploit by keeping their Macs physically secure and avoiding the insertion of untrusted USB-C cables and devices.
Article Link: Apple's T2 Security Chip Vulnerable to Attack Via USB-C
Right. Avoid USB-C models... so Mid 2015 MacBook Pro...So you're not buying macs anymore?
Yes. A reboot fixes it unless the device is still connected. And it’s a device, not just a cable. The cable allows the device to do what it wants to do.
Big question: does it bypass password login? If not, it requires this thing to be discretely connected directly to the usb-c on the computer and the owner not noticing. Or if I am missing something?
Apple should release devices without USB. That appears to be the real issue.
Dr. Katherine Pulaski said:That's like destroying the disease by killing the patient!
And then trash them once the battery drains fully. /sApple should release devices without USB. That appears to be the real issue.
It's not as if USB has never been implicated in any type of security vulnerability prior to this.Hmm... Got it. Star Trek: The Next Generation, season 2, episode 2: Where Silence has Lease.
You're essentially taking out the attack vector without fixing the source of the vulnerability, which is the T2 chip. Fix that going forward so you don't have that problem with future Macs.
However, this could lead to a recall of those affected Macs so they can be fixed. But taking out the method of which to attack doesn't fix the source of the problem.
BL.