If I’m understanding this correctly, it’s the mere existence of reloader.efi and the fact that Microsoft signed it that’s the problem.
ESET first discovered CVE-2024-7344 in July 2024. Since then, all vulnerable applications have been fixed, and Microsoft revoked the old, vulnerable binaries in its Jan. 14, 2025, Patch Tuesday update.
So Microsoft are just signing anything even if it breaks UEFI security? And presumably, now that this file is out there, it can be used to subvert SecureBoot on any system that hasn’t had its UEFI blacklist updated?
threaded - newest
If I’m understanding this correctly, it’s the mere existence of reloader.efi and the fact that Microsoft signed it that’s the problem.
So Microsoft are just signing anything even if it breaks UEFI security? And presumably, now that this file is out there, it can be used to subvert SecureBoot on any system that hasn’t had its UEFI blacklist updated?
Oh great, Microsoft, good job.
Pretty much every Secure Boot device trusts Microsoft by default, which is why I think it’s pretty much useless (in its default state anyway).