Due to Secure Boot (if it actually enabled since there are some bogous implementations) this can be prevented. If I understand it correctly, LogoFAIL bypasses this security measure and enables loading unsigned code.
Comment on Just about every Windows and Linux device vulnerable to new LogoFAIL firmware attack
gnutrino@programming.dev 6 months agoIf you have access to directly write to arbitrary disk locations you already have full control. Why bother with overwriting the logo file with a malicious payload if you can just overwrite the actual kernel…
ClemaX@lemm.ee 6 months ago
Cocodapuf@lemmy.world 6 months ago
This is what I’m wondering
surewhynotlem@lemmy.world 6 months ago
Because this can persist beyond an OS rebuild or patch. You infect the BIOS and you’re on the device until the BIOS is free reflashed. And who ever does that?
Cocodapuf@lemmy.world 6 months ago
Or until you overwrite that malicious logo again?
surewhynotlem@lemmy.world 6 months ago
No. The logo is loaded, runs in BIOS context and is able to modify the BIOS. Now it’s embedded and the logo is irrelevant.