Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Endpoint Security

12/16/2019
10:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

With Plundervolt, an Intel Processor's Secure Enclave Is No Longer Secure

Major hardware vulnerability can allow the changing of information that is supposedly stored as secure in the chip's Secure Enclave.

International researchers have discovered a major hardware vulnerabilitythat they call Plundervolt in most of the modern Intel processors from Skylake onward. It can allow the changing of information that is supposedly stored as secure in the chip's Secure Enclave.

The researchers have a web page with a snazzy logo (designed by Mike Stimpson) dedicated to the vulnerability (CVE-2019-11157) where they attempt to answer some general questions about it.

The vulnerability has been known since June by the group who then informed Intel. It's taken Intel until now to get a patch out to mitigate things. Admittedly, the problems that Intel had to navigate in a solution composed of both microcode (CPU firmware) and BIOS updates were non-trivial.

The method used in the attack is similar to how a gamer might "overclock" a CPU for faster performance in that it uses a privileged power/clock management feature (the CPU's Dynamic Voltage and Frequency Scaling) to do its dirty work: inject faults into a trusted execution environment. These faults can then be actively exploited later by the attacker once the malware program leaves the enclave and is running in its normal space. Thus Plundervolt does not break the SGX in the usual sense, instead it poisons the output.

By the way, this is just the opposite of recent speculative-style SGX attacks like Foreshadow or Spectre. Those methods allow the attacker to read data from SGX enclave memory (i.e. attacks the confidentiality). As the researchers note, "Plundervolt achieves the complementary operation, namely changing values in SGX-protected memory (i.e. attacks the integrity)".

The problem affects many users, not just those using SGX for cryptography programs for example. The group says that Plundervolt can also cause memory safety misbehavior in certain scenarios. For example, the paper finds that out-of-bounds accesses may arise when an attacker faults multiplications emitted by the compiler for array element indices or pointer arithmetic.

They conclude that Plundervolt can break a processor's integrity guarantees, affecting even securely written code. They also claim to show that Plundervolt may affect SGX's attestation functionality, which undermines the building blocks underpinning the security of Intel's SGX ecosystem. The Gang of Six says that, "this represents the first practical attack that directly breaches the integrity guarantees in the Intel SGX security architecture."

Yow.

But there is a bit of upside to all of this. Evidently, Plundervolt can't be exploited remotely. Pointing the victim to malware with JavaScript in it won't get the vulnerability to work.

Plundervolt also doesn't work from within virtualized environments, such as virtual machines and cloud computing services, because that vector was considered by Intel in the design of the SGX architecture. At least in this version of Plundervolt (which doesn't break that architecture), it prevents that kind of exploit.

So, those wanting to close off SGX's possible corruption should patch both the CPU microcode and the BIOS of a machine. Nothing less than that will mitigate the vulnerability.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Look Beyond the 'Big 5' in Cyberattacks
Robert Lemos, Contributing Writer,  11/25/2020
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: I think the boss is bing watching '70s TV shows again!
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5423
PUBLISHED: 2020-12-02
CAPI (Cloud Controller) versions prior to 1.101.0 are vulnerable to a denial-of-service attack in which an unauthenticated malicious attacker can send specially-crafted YAML files to certain endpoints, causing the YAML parser to consume excessive CPU and RAM.
CVE-2020-29454
PUBLISHED: 2020-12-02
Editors/LogViewerController.cs in Umbraco through 8.9.1 allows a user to visit a logviewer endpoint even if they lack Applications.Settings access.
CVE-2020-7199
PUBLISHED: 2020-12-02
A security vulnerability has been identified in the HPE Edgeline Infrastructure Manager, also known as HPE Edgeline Infrastructure Management Software. The vulnerability could be remotely exploited to bypass remote authentication leading to execution of arbitrary commands, gaining privileged access,...
CVE-2020-14260
PUBLISHED: 2020-12-02
HCL Domino is susceptible to a Buffer Overflow vulnerability in DXL due to improper validation of user input. A successful exploit could enable an attacker to crash Domino or execute attacker-controlled code on the server system.
CVE-2020-14305
PUBLISHED: 2020-12-02
An out-of-bounds memory write flaw was found in how the Linux kernel’s Voice Over IP H.323 connection tracking functionality handled connections on ipv6 port 1720. This flaw allows an unauthenticated remote user to crash the system, causing a denial of service. The highest threat ...