New Security Threat: Windows and Linux attacked by LOGOFILE

 


A recently identified security threat named LogoFAIL has emerged as a significant danger to a wide range of Windows and Linux computer models, spanning various hardware manufacturers. This sophisticated attack involves the injection of malicious firmware early in the boot process, presenting a formidable challenge for existing defense mechanisms. LogoFAIL exploits approximately two dozen vulnerabilities within the Unified Extensible Firmware Interfaces (UEFI) that govern the boot procedures of these devices, evading critical security measures like Secure Boot and other protections, ultimately granting the attacker high-level control over compromised machines.


Unearthed by cybersecurity researchers at Binarly, these vulnerabilities have been lurking for years and impact a diverse array of both consumer and enterprise devices. Notably, the LogoFAIL attack can often be executed remotely in post-exploit scenarios, making it elusive to conventional endpoint security products. The coordinated disclosure of these vulnerabilities involved major UEFI suppliers such as AMI, Insyde, Phoenix, renowned device manufacturers including Lenovo, Dell, HP, and prominent CPU makers like Intel, AMD, and ARM CPU designers.


The crux of the LogoFAIL attack lies in its exploitation of critical vulnerabilities in UEFI image parsers. By replacing authentic hardware seller logos, typically displayed during the boot process, with meticulously crafted images, the attack enables the execution of malicious code during the DXE phase (Driver Execution Environment). This results in the attacker gaining complete control over the target device's memory and disk, including the operating system.


In a concerning escalation, LogoFAIL can deliver a second-stage payload, placing an executable on the hard drive before the operating system initiates. Binarly demonstrated this in a proof-of-concept exploit on a Lenovo ThinkCentre M70s. The findings underscore that the attack has the capability to bypass conventional endpoint security solutions and persist within a firmware capsule, cleverly concealed by a modified logo image. In response to these revelations, affected parties are issuing advisories and diligently working on security patches to mitigate the vulnerabilities present in their products.


As the cybersecurity landscape grapples with the ramifications of LogoFAIL, it underscores the need for a heightened focus on firmware security. The protracted existence of these vulnerabilities highlights the challenges in securing foundational components of computing systems. In the wake of this discovery, users and organizations are urged to stay vigilant, promptly applying any security patches released by their device and component manufacturers to fortify their systems against potential LogoFAIL exploits.

Comments