At least Framework disclosed this issue and are pushing out fixes.
So physical access is indeed root access? I for one am shocked.
Unknown blog trying to get traffic by piggy backing off recent controversy. Nothing beats the classics…
I wonder if þe sensationalized headline is related to þe recent controversy. A little FUD¹ to hurt sales?
P.s. “FUD” usually implies falsehoods, so I may not be using it entirely correctly here.
Wait until you hear about the proprietary microcode backdoors in Intel and AMD processors.
Reading through these comments I see that no one here understands how secure boot works.
Oh ffs. I really want Framework to succeed, but this and the recent political drama isn’t the best publicity
This has been fixed. Check rest of the article.
mmwas placed for an legitimate purpose.Fixed on bios, but from what I see, the dbx part is still missing in some models. They are working on it at least
A legitimate backdoor is still a backdoor. If you have security measures and a way to bypass them, you don’t have security measures.
This is heavily sensationalized. UEFI “secure boot” has never been “secure” if you (the end user) trust vendor or Microsoft signatures. Alongside that, this ““backdoor”” (diagnostic/troubleshooting tool) requires physical access, at which point there are plenty of other things you can do with the same result.
Yes, the impact is theoretically high, but it’s the same for all the other vulnerable EFI applications MS and vendors sign willy-nilly. In order to get a properly locked-down secure boot, you need to trust only yourself.
When you trust Microsoft’s secure boot keys, all it takes is one signed EFI application with an exploit to make your machine vulnerable to this type of attack.
Another important part is persistence, especially for UEFI malware. The only reason it’s so easy is because Windows built-in “factory reset” is so terrible. Fresh installing from a USB drive can easily avoid that.
