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

11/16/2018
08:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

New Spectre & Meltdown Attacks Show Limits of CPU Vulnerabilities

A group of researchers from Belgium, Austria and the US have uncovered more Spectre and Meltdown flaws in CPU architectures, but their paper also shows the limits of these vulnerabilities in real-world attacks.

The class of CPU side-channel vulnerabilities dubbed Spectre and Meltdown arose suddenly in the early part of this year. These hardware flaws are the result of exception or branch misprediction events that can leave secret-dependent traces in the chip's microarchitectural state.

The style of CPU architecture that allows these vulnerabilities has been in use since 1995. (See MIT Researchers Have a DAWG in the Fight Against Spectre & Meltdown.)

Spectre-style attacks break the isolation between applications that is enforced by CPU memory management. Meltdown-style attacks break the fundamental isolation between user applications and the operating system.

The chip industry has been exceedingly busy trying to fix with ad-hoc defenses -- microcode and software patches -- these vulnerabilities, as well as other variants, which have been obviously broken for decades. (See Intel's 9th Gen Processors Offer Protections Against Spectre & Meltdown .)

However, what has not been done up until now is to try and figure out the underlying problems that make these attacks possible.

In a paper entitled, "A Systematic Evaluation of Transient Execution Attacks and Defenses," nine academics -- including those who first discovered Spectre and Meltdown -- try to perform what they deem "a sound and extensible systematization of transient execution attacks." Rather than concentrate on specific examples of attacks, they attempt to draw a wider perspective on all the possible hardware areas that can be attacked.

The researchers use the term "transient execution attacks" since the attacks focus on the CPU hardware that affects instructions, which are executed transiently: The instructions and operations are first created by the extensions in the CPU pipeline, and then they vanish.

Importantly, the researchers note that "transient execution attacks are not limited to the cache: any microarchitectural state that can be changed and observed can be used."

Most attacks seen thus far have used cache state as the way they infer what is really going on in the CPU. To stress that there are more side-channels than just a cache is an important point the researchers make.

By focusing on the hardware areas one-by-one, the researchers found new kinds of attacks as well as ones that would not work.

As far as Meltdown goes, the ones that worked were Meltdown-BR, which exploits an x86 bound instruction on Intel and AMD CPUs, and Meltdown-PK, which bypasses memory protection keys on Intel CPUs.

The academics also found Meltdown attacks did not work on memory alignment check exceptions, division by zero errors, the supervisor mode access prevention (SMAP) mechanism, out-of-limit segment accesses, invalid opcode exception, and non-executable memory.

Three new Spectre attacks that involve the Pattern History Table mechanism were also found, as well as two new ones that use the Branch Target Buffer as a target. The new attacks were possible on AMD, ARM, and Intel CPUs.

Overall, what the paper presents is not truly earth shattering.

It's more an extension of what has already been observed with more detail and texture given. The way that the researchers look at defenses against these sort of exploits is only theoretical. In the paper, they acknowledge that "we need to think about future defenses carefully and plan to mitigate attacks and variants that are unknown."

Yes, the researchers found seven new kinds of attacks. But that is balanced by the group finding six kinds of attacks that we probably don't have to worry about.

Related posts:

— 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
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
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-27218
PUBLISHED: 2020-11-28
In Eclipse Jetty version 9.4.0.RC0 to 9.4.34.v20201102, 10.0.0.alpha0 to 10.0.0.beta2, and 11.0.0.alpha0 to 11.0.0.beta2, if GZIP request body inflation is enabled and requests from different clients are multiplexed onto a single connection, and if an attacker can send a request with a body that is ...
CVE-2020-29367
PUBLISHED: 2020-11-27
blosc2.c in Blosc C-Blosc2 through 2.0.0.beta.5 has a heap-based buffer overflow when there is a lack of space to write compressed data.
CVE-2020-26245
PUBLISHED: 2020-11-27
npm package systeminformation before version 4.30.5 is vulnerable to Prototype Pollution leading to Command Injection. The issue was fixed with a rewrite of shell sanitations to avoid prototyper pollution problems. The issue is fixed in version 4.30.5. If you cannot upgrade, be sure to check or sani...
CVE-2017-15682
PUBLISHED: 2020-11-27
In Crafter CMS Crafter Studio 3.0.1 an unauthenticated attacker is able to inject malicious JavaScript code resulting in a stored/blind XSS in the admin panel.
CVE-2017-15683
PUBLISHED: 2020-11-27
In Crafter CMS Crafter Studio 3.0.1 an unauthenticated attacker is able to create a site with specially crafted XML that allows the retrieval of OS files out-of-band.