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
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/17/2020
Cybersecurity Bounces Back, but Talent Still Absent
Simone Petrella, Chief Executive Officer, CyberVista,  9/16/2020
Meet the Computer Scientist Who Helped Push for Paper Ballots
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5421
PUBLISHED: 2020-09-19
In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the browser used through the use of a jsessionid path parameter.
CVE-2020-8225
PUBLISHED: 2020-09-18
A cleartext storage of sensitive information in Nextcloud Desktop Client 2.6.4 gave away information about used proxies and their authentication credentials.
CVE-2020-8237
PUBLISHED: 2020-09-18
Prototype pollution in json-bigint npm package < 1.0.0 may lead to a denial-of-service (DoS) attack.
CVE-2020-8245
PUBLISHED: 2020-09-18
Improper Input Validation on Citrix ADC and Citrix Gateway 13.0 before 13.0-64.35, Citrix ADC and NetScaler Gateway 12.1 before 12.1-58.15, Citrix ADC 12.1-FIPS before 12.1-55.187, Citrix ADC and NetScaler Gateway 12.0, Citrix ADC and NetScaler Gateway 11.1 before 11.1-65.12, Citrix SD-WAN WANOP 11....
CVE-2020-8246
PUBLISHED: 2020-09-18
Citrix ADC and Citrix Gateway 13.0 before 13.0-64.35, Citrix ADC and NetScaler Gateway 12.1 before 12.1-58.15, Citrix ADC 12.1-FIPS before 12.1-55.187, Citrix ADC and NetScaler Gateway 12.0, Citrix ADC and NetScaler Gateway 11.1 before 11.1-65.12, Citrix SD-WAN WANOP 11.2 before 11.2.1a, Citrix SD-W...