![]() ![]() I'm not a security expert but as a developer have a base understanding, these sort of things, it tends to muddy up trying to diagnose the problem. ![]() When trying to explain this, I'd really recommend steering away from rampant speculation like "permanent" "unpatchable". edit 2: looks like it happens on a MacBook 2017, video forthcoming tomorrow or Friday. I think you need to give a really detailed break down (Intel? Have you disabled System Integrity protection?) Rebooting, I was not able to bypass the Activation Lock, it would not boot into recovery. My M1 Max promptly rebooted when locked, then boot into Active my Mac. edit: I just tried this on M1 Max locking it from my M1 Pro. Also, declaring it "unpatchable" seems like jumping the gun. Is this correct? I may try this tonight as I have multiple Macs as I'm a bit dubious about it. Reboot the device and it will now be out of the Locked mode, and will boot to the standard login screen.Take said Mac and launch it into recovery mode.This is accomplished by going to iCloud and using the iCloud Find Devices interface. From another device, Lock your Mac via Find Device.U/UnfuckYourEmploymentI had to re-read this as it's surprisingly unclear, I think this is what you're trying to say: They finally responded with this statement today. I gave them every opportunity to treat this as a serious security concern. ![]() There may still be a vulnerability there, using a different recovery mode key sequence, but I am unable to validate it due to lack of access to Apple Silicon.īecause of all the hate I’m getting, here’s Apple’s response to this vulnerability. Multiple users were unable to validate on M1/M2. u/BourbonicFisky tested and was able to validate this on a 2017 Intel. I had initially discovered it on my 2019 Intel MBP. It’s unpatchable because it’s possible to revert to a vulnerable version of MacOS using Apple Configurator 2. You’re at the user login screen and the device is now unlocked on your iCloud account. Hold Command-Option-R, wait until the password prompt. Lock your Mac in Find My, using a different device.Īllow the device to reboot to PIN code screen. You, as a Mac user, deserve to know the risk. I have no idea why Apple does not consider this a security concern, but it is a concern, and one that they apparently have no intention of resolving, or at least acknowledging as an issue in that report. In the worst case scenario, if someone steals your Mac and knows your password, they have access to everything on your system, even if you flag the device as lost. In the best case scenario, this means that the anti-theft measure is completely irrelevant. The lack of token validation means that after doing the bypass on the Mac device, it is automatically unlocked on the iCloud account used to lock it, without any user or account validation. This vulnerability exists because of two reasons the firmware, which is stored on the actual device hard disk, and the fact that iCloud does not conduct token validation between iCloud and the device itself. Obviously this is a major security concern for all Intel Mac devices, as it requires no exploitation and cannot be patched, due to the fact that it is possible to reinstall earlier, unpatched Mac versions. So I would like to preface this by stating clearly: I reported it to Apple, and they determined it is not a security concern.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |