Yet Another Major Security Deficiency in UEFI
- Dr. Roy Schestowitz
- 2015-05-27 11:03:53 UTC
- Modified: 2015-05-27 11:03:53 UTC
Another reason to reject UEFI: system compromise before boot sequence starts (e.g. GNU/Linux)
Summary: UEFI is inherently insecure, more so than the alternatives which it strives to replace, including Free/libre ones
INTEL'S UEFI has been marketed as 'security' because of "Restricted Boot", which basically gives a bunch of companies like Microsoft control over one's computer. Microsoft works closely with the NSA and the NSA already spoke about compromise at boot time. UEFI enables remote bricking of PCs -- a subject that we covered here before, e.g. in:
There is a post titled
"UEFI backdoor allows root exploit in Linux" which
UEFI apologist and developer Matthew Garrettresponded to not exactly with refutation, only the insistence that it is not the "backdoor you are looking for". To quote: "And that's what Dmytro has done - he's written code that sits in that hidden area of RAM and can be triggered to modify the state of the running OS. But he's modified his own firmware in order to do that, which isn't something that's possible without finding an existing vulnerability in either the OS or (or more recently, and) the firmware. It's an excellent demonstration that what we knew to be theoretically possible is practically possible, but it's not evidence of such a backdoor being widely deployed."
Maybe not yet. We're talking about and dealing with imperialistic espionage agencies that go as far as putting back doors in the firmware of just about every hard drive.
We really need to stop referring to UEFI as a security enhancement. This is far from the first time security issues are found in UEFI, which is complicated, proprietary, patents-encumbered and relatively immature.
Computers with UEFI should be appropriately labeled (warning labels), just like foods with genetically-modified ingredients or packets of cigarettes.
⬆