4 ms·
> Are UEFI rootkits an actual concern, like are they common in the wild? If one segment needs to worry about UEFI rootkits, it's cloud vendors. Very dedicated
by judge2020 6y ago
> Are UEFI rootkits an actual concern, like are they common in the wild?
If one segment needs to worry about UEFI rootkits, it's cloud vendors. Very dedicated (nation-state sponsored) attackers could burn/use a zero-day hypervisor escape to installs a UEFI rootkit that tampers with the processor's integrated HSM (as said in the article, tampering with it has already happened and the exploits have been patched by AMD). As I understand it, If a vendor uses full memory encryption, the above exploit could lead to decrypting and exfiltrating other customers' data.
- boring_twenties 6y agoCloud vendors should be using coreboot, not UEFI.
- freeone3000 6y agoOne of the cloud vendors created UEFI.
- boring_twenties 6y agoThen they know full well how bad it is! *Jokes aside, I think Intel created UEFI (for Itanium?), not Microsoft?
- freeone3000 6y agoThe consortium has AMD, Intel, and Microsoft listed as contributors, so even if they didn't initially create the thing, they had a hand in it. The executable format used for UEFI is PE, which is telling.
- octoberfranklin 6y agoNot sure why downvoted. I run blobless coreboot for precisely this reason. My only regret is not being able to find newer x86_64 gear that supports it. OTOH you can still buy in-production arm64 boxes that boot with zero blobs (RK3399).
- numpad0 6y agoAttacker might flash a tampered BIOS from inside a VM makes total sense. It’s surprising how many SPI ROM there can be in a box, and how basically they’re all waiting there to be exploited.