Multiple Unified Extensible Firmware Interface (UEFI) implementations are vulnerable to code execution in System Management Mode (SMM) by an attacker who gains administrative privileges on the local machine. An attacker can corrupt the memory using Direct Memory Access (DMA) timing attacks that can lead to code execution. These threats are collectively referred to as RingHopper attacks.
The UEFI standard provides an open specification that defines a software interface between an operating system (OS) and the device hardware on the system. UEFI can interface directly with hardware below the OS using SMM, a high-privilege CPU mode. SMM operations are closely managed by the CPU using a dedicated portion of memory called the SMRAM. The SMM can only be entered through System Management Interrupt (SMI) Handlers using a communication buffer. SMI Handlers are essentially a system-call to access the CPU's SMRAM from its current operating mode, typically Protected Mode.
A race condition involving the access and validation of the SMRAM can be achieved using DMA timing attacks that rely on time-of-use (TOCTOU) conditions. An attacker can use well-timed probing to try and overwrite the contents of SMRAM with arbitrary data, leading to attacker code being executed with the same elevated-privileges available to the CPU (i.e., Ring -2 mode). The asynchronous nature of SMRAM access via DMA controllers enables the attacker to perform such unauthorized access and bypass the verifications normally provided by the SMI Handler API.
The Intel-VT and Intel VT-d technologies provide some protection against DMA attacks using Input-Output Memory Management Unit (IOMMU) to address DMA threats. Although IOMMU can protect from DMA hardware attacks, SMI Handlers vulnerable to RingHopper may still be abused. SMRAM verification involving validation of nested pointers adds even more complexity when analyzing how various SMI Handlers are used in UEFI.
An attacker with either local or remote administrative privileges can exploit DMA timing attacks to elevate privileges beyond the operating system and execute arbitrary code in SMM mode (Ring -2). These attacks can be invoked from the OS using vulnerable SMI Handlers. In some cases, the vulnerabilities can be triggered in the UEFI early boot phases (as well as sleep and recovery) before the operating system is fully initialized.
A successful attack enables any of the following impacts:
- Invalidation or bypass of UEFI security features (SecureBoot, Intel BootGuard).
- Installation of persistent software that cannot be easily detected or erased.
- Creation of backdoors and back communications channels to exfiltrate sensitive data
- Interruption of system execution leading to permanent shutdown.
Because these attacks are against UEFI supported firmware, OS and EDR solutions may have diminished visibility into unauthorized access.
Install the latest stable version of UEFI firmware provided by your PC vendor or by the reseller of your computing environments. See the links below for resources and updates provided by specific vendors to address these issues.
If your operating system supports automatic or managed updates for firmware, such as Linux Vendor Firmware Service (LVFS), check (
fwupdmgr get-updates) and apply the firmware updates provided by LVFS using
fwupdmgr update as appropriate.
Thanks to the Intel iStare researchers Jonathan Lusky and Benny Zeltser who discovered and reported this vulnerability.
This document was written by Vijay Sarvepalli and Jeffrey S. Havrilla.
Hewlett Packard Enterprise Affected
Insyde Software Corporation Affected
AMD Not Affected
Phoenix Technologies Not Affected
Toshiba Corporation Not Affected
ASUSTeK Computer Inc. Unknown
Gamma Tech Computer Corp. Unknown
GETAC Inc. Unknown
HP Inc. Unknown
NEC Corporation Unknown
Star Labs Online Limited Unknown
VAIO Corporation Unknown