A significant vulnerability in Microsoft’s Secure Boot system was revealed when researchers at ESET identified 11 firmware images, with some dating back to 2013, that contained known defects but remained digitally signed by Microsoft without revocation. These components, called shims, were originally designed to extend Secure Boot protections to Linux devices and utility software.
Secure Boot is a security mechanism embedded in device motherboards that was introduced in 2012 to prevent firmware infections and bootkit malware. The vulnerability allows attackers to use simple techniques to completely circumvent these protections by leveraging old, unrevoked shim binaries. Once installed, an attacker can subvert the boot process and install malicious firmware that persists even after operating system reinstallation or hard drive replacement.
The vulnerability affects both Windows and Linux users. Various Linux distributors including Red Hat, OpenSUSE, and Oracle, as well as third-party software providers, utilized these vulnerable shims. Some of the affected shims lack newer security protections such as SBAT and MOK deny lists, while others contain accumulated code bugs or authorize second-stage binaries with known vulnerabilities. The skill level required to exploit many of these vulnerabilities is low.
Microsoft’s failure to revoke the shims stems partly from the extreme complexity of Secure Boot’s revocation system. The mechanism relies on multiple databases with limited storage space and various version-based revocation methods including SBAT and Secure Boot Security Version Number enforcement. Microsoft finally revoked the 11 shims in June following notification from ESET and CERT. The company has not publicly explained how the decade-long lapse occurred.
Industry experts have criticized the Secure Boot model itself, noting that Microsoft’s role as the de facto root of trust for the UEFI platform, combined with the system’s inability to scale properly and allow components to boot after certificates expire, creates fundamental structural problems that extend beyond this particular incident.
Article Attribution | Read More at Article Source
Article summary produced by Claude AI