177
Just about every Windows and Linux device vulnerable to new LogoFAIL firmware attack
(arstechnica.com)
this post was submitted on 06 Dec 2023
177 points (95.9% liked)
Technology
59105 readers
3244 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
They need to be able to place a malicious file in EFI boot partition or in an unsigned section of a firmware update. Holes in the libraries that parse images for display on preboot.
What if I disable UEFI splash screen? I always do that if possible. Not due to this, but because I prefer a bunch of text over a lame logo.
No way to know. It depends on how whoever did your firmware handled it. The idea is that there's an overflow or something in the image parser. If the person writing your firmware code still parses the image even if it's not displayed, you'd still get the pointy end. (and at that point, they're bypassing secure boot)
Don't sweat it too much, the file has to get there somehow before it can even be an issue. So someone needs to write to your UEFI partition or get you to flash a bad bios. It's just an inside vector not a direct attack. I'll be good for people to update their damn image processing, but the likely hood of getting shived in the wild is pretty low.
I wonder.. could one put their UEFI partition on a flash drive, then remove after booting? Or just dismount the partition, but physical separation sounds better