Binarly's research blog on firmware and UEFI security, covering Secure Boot bypasses, LogoFAIL, PKfail and BMC vulnerabilities.
HN treats it as a primary source on UEFI flaws like LogoFAIL and PKfail, and commenters prefer it to rewrites in other outlets.
there are 3 paths.
1. placing logo into ESP (EFI System Partition) via admin privileges
2. Bios update tool
3. When there is no expected way to customize the logo, it is still possible via physical attack vector: just with an SPI flash programmer if a logo is not covered with any hardware-based Verified Boot technology like Intel Boot Guard or AMD Hardware-Validated Boot
“As we can see in the following table, we detected parsers vulnerable to LogoFAIL in hundreds of devices sold by Lenovo, Supermicro, MSI, HP, Acer, Dell, Fujitsu, Samsung and Intel. “
https://binarly.io/posts/finding_logofail_the_dangers_of_image_parsing_during_system_boot/
The binarly post[0] (submitted by @skilled 2 days ago /w no comments and little upvote love) is a cleaner source[1] and just as easy to read. This seems to be a bit of a rewrite, bit of a copy/paste (images straight from binarly). The vulnerability was published a week ago, this article implies it was disclosed today.
[0]: https://binarly.io/posts/The_Far_Reaching_Consequences_of_LogoFAIL/
[1]: https://news.ycombinator.com/item?id=38515571
Hello, I am the Bootkitty developer. The reason our bootkit is self-signed is because it uses the LogoFAIL vulnerability to register a MOK on the system to bypass secureboot, which is why our signature is included. I will leave an analysis article about LogoFAIL at the link below. https://www.binarly.io/blog/logofail-exploited-to-deploy-bootkitty-the-first-uefi-bootkit-for-linux
The root of trust in Secure Boot is typically an OEM certificate, not Microsoft's, which is probably even worse: https://www.binarly.io/blog/pkfail-untrusted-platform-keys-undermine-secure-boot
In any case, you're free to remove Microsoft's certificates and enroll your own.
https://eclypsium.com/blog/understanding-detecting-pixiefail-uefi-vulnerabilities/
https://binarly.io/posts/The_Far_Reaching_Consequences_of_LogoFAIL/