News New UEFI vulnerability bypasses Secure Boot — bootkits stay undetected even after OS re-install

I can only joke, with some irony (and even malice), that antivirus companies will have to develop exploits in OS and UEFI to defeat the enemy. First of all, to independently penetrate the -2 ring when they do not have enough privileges, as usually happens with malicious viruses and exploits that try to get from the 3 ring to 2,1,0,-1,-2... -3 is inaccessible to anyone (except US intelligence agencies) - this is the level of undocumented malware called Intel ME/AMD PSP...
 
The more complications they add, the more vulnerabilities they open up.

It's not a complexity error, it's a major conceptual flaw: they make UEFI and they provided a tool to help update it, they added the security checks in the update tool instead of UEFI. The update tool is not required, it use UEFI functions, any developpers wanting to streamline the process can make it in its own application without calling the update tool, that's the list of applications provided.
 
So much for the much praised UEFI being so secure, a bit like needing TPM2 being needing to be secure, just another sales pitch from Intel, Microsoft and the mega corps ripping off the consumers to force purchases.
 
Bah! Back in the day, a BIOS chip was 8kB. Nowadays they can be 32MB--and Windows 3.11 only required 10MB of disk space free to install. Pretty soon there'll be enough space to install NT in there.

I guess it has to be that big now to hold the firmware for the Intel Management Engine or AMD Platform Security Processor, both being a separate computer within your computer that runs all of the time (even when the main computer is asleep) and has access to memory and network which can bypass any OS firewall to phone home. What could go wrong?