A newly identified vulnerability, dubbed PKfail, poses a significant security risk to a wide range of computer models by allowing attackers to bypass Secure Boot protections. Discovered by the firmware and software supply chain security firm Binarly, PKfail is associated with an exposed American Megatrends International (AMI) Platform Key (PK) that was never intended for use in production environments. The issue arises from the fact that this default key, meant for development purposes, was inadvertently included in numerous devices from major manufacturers such as Dell, HP, Lenovo, Fujitsu, and Supermicro.
The PKfail vulnerability enables attackers to sign and execute malicious code during the device’s boot process, even when Secure Boot is enabled. This can lead to the installation of UEFI bootkits, such as BlackLotus, which compromise the system’s security from the firmware level up to the operating system. Binarly’s research shows that the flaw affects devices with firmware dating from as early as May 2012 to as recently as June 2024. This extensive timeframe highlights the enduring nature of the issue and the wide-reaching impact it has across various device models.
In response to the vulnerability, some manufacturers have acted to mitigate the risk. Supermicro has issued a fix, and Dell, which worked closely with Binarly, has also addressed the issue in its products. However, HP, Lenovo, and Fujitsu have stated that their currently supported products are not impacted by this vulnerability, suggesting varying levels of exposure and response across the industry. The mixed responses underscore the importance of proactive security measures and timely updates in the face of such vulnerabilities.
To aid users in determining if their systems are affected, Binarly has developed a detection tool and published demonstration videos showing how PKfail can be exploited on both Windows and Linux platforms. This tool allows users to check their devices and take necessary actions to protect themselves. The PKfail vulnerability serves as a stark reminder of the critical need for thorough security practices in the firmware supply chain to prevent such significant risks from materializing.
Reference:
