this post was submitted on 06 Dec 2023
311 points (97.0% liked)

Linux

48245 readers
586 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] _edge@discuss.tchncs.de 143 points 11 months ago (21 children)

There are several ways to exploit LogoFAIL. Remote attacks work by first exploiting an unpatched vulnerability in a browser, media player, or other app and using the administrative control gained to replace the legitimate logo image processed early in the boot process with an identical-looking one that exploits a parser flaw. The other way is to gain brief access to a vulnerable device while it’s unlocked and replace the legitimate image file with a malicious one.

In short, the adversary requires elevated access to replace a file on the EFI partition. In this case, you should consider the machine compromised with or without this flaw.

You weren't hoping that Secure Boot saves your ass, were you?

[–] InnerScientist@lemmy.world 15 points 11 months ago (4 children)

replace a file on the EFI partition.

Doesn't this mean that secure boot would save your ass? If you verify that the boot files are signed (secure boot) then you can't boot these modified files or am I missing something?

[–] fl42v@lemmy.ml 4 points 11 months ago* (last edited 11 months ago) (1 children)

If it can execute in ram (as far as I understand, they've been talking about fileless attacks, so... Possible?), it can just inject whatever

Addit: also, sucure boot on most systems, well, sucks, unless you remove m$ keys and flash yours, at least. The thing is, they signed shim and whatever was the alternative chainable bootloader (mako or smth?) effectively rendering the whole thing useless; also there was a grub binary distributed as part of some kaspersky's livecd-s with unlocked config, so, yet again, load whatever tf you want

[–] InnerScientist@lemmy.world 3 points 11 months ago (1 children)

Last time I enabled secure boot it was with a unified kernel image, there was nothing on the EFI partition that was unsigned.

Idk about the default shim setup but using dracut with uki, rolled keys and luks it'd be secure.

After this you're protected from offline attacks only though, unless you sign the UKI on a different device any program with root could still sign the modified images itself but no one could do an Evil Maid Attack or similar.

[–] fl42v@lemmy.ml 1 points 11 months ago

The point with m$ keys was that you should delete them as they're used to sign stuff that loads literally anything given your maid is insistent enough.

[note: it was mentioned in the arch wiki that sometimes removing m$ keys bricks some (which exactly wasn't mentioned) devices]

load more comments (2 replies)
load more comments (18 replies)