Binarly Blog
binarly.io · Company blog · on HN since 2022
Binarly's research blog on firmware and UEFI security, covering Secure Boot bypasses, LogoFAIL, PKfail and BMC vulnerabilities.
What HN saysHN treats it as a primary source on UEFI flaws like LogoFAIL and PKfail, and commenters prefer it to rewrites in other outlets.
22HN people shared it
5linked it in comments
18stories submitted
284story points
3 months agolast shared
2022people per year2026
Most-shared posts
- 1Finding LogoFAIL: The Dangers of Image Parsing During System Boot3 people · 2 points · first shared 2023 · discussion on HN
- 2LogoFAIL: Secure Boot bypass with manipulated boot logos3 people · 1 points · first shared 2023 · discussion on HN
- 3An In-Depth Look at the 23 High-Impact Vulnerabilities2 people · 16 points · first shared 2022 · 2 comments on HN
- 4PKfail: Untrusted Platform Keys Undermine Secure Boot on UEFI Ecosystem2 people · 9 points · first shared 2024 · 1 comments on HN
- 5Another Crack in the Chain of Trust: Uncovering (Yet Another) Secure Boot Bypass1 people · 126 points · first shared 2025 · 137 comments on HN
- 6XZ Utils Backdoor Still Lurking in Docker Images1 people · 113 points · first shared 2025 · 58 comments on HN
- 7FirmwareBleed: The industry fails to adopt Return Stack Buffer mitigations in S1 people · 3 points · first shared 2022 · discussion on HN
- 8Broken Trust: Fixed Supermicro BMC Bug Gains New Life in Two New Vulnerabilities1 people · 3 points · first shared 2025 · discussion on HN
- 9Clevo Boot Guard Keys Leaked in Update Package1 people · 2 points · first shared 2025 · 1 comments on HN
- 10BeneFITs: Bypassing Signature Verification in U-Boot SPL1 people · 2 points · first shared 2026 · discussion on HN
- 11UEFI Bootkit Hunting: In-Depth Search for Unique Code Behavior1 people · 2 points · first shared 2025 · discussion on HN
- 12SMM memory corruption vulnerability in SMM module on Gigabyte device/SMRAM write1 people · 2 points · first shared 2025 · discussion on HN
- 13HP Devices – Vulnerabilities in Firmware1 people · 1 points · first shared 2022 · discussion on HN
- 14Unfit to Boot: Breaking U-Boot's Fit Signature Verification1 people · 1 points · first shared 2026 · discussion on HN
- 15High-Impact Vulnerabilities in Firmware Impacting Millions of Enterprise Devices1 people · 1 points · first shared 2022 · discussion on HN
What HN people wrote when they linked it
instagib · 2023-12-06
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…
gnabgib · 2023-12-06
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
ZeroWidthJoiner · 2026-06-09
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-s…
In any case, you're free to remove Microsoft's certificates and enroll your own.
B1ack3at_ · 2024-12-03
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…