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.

Vulnerabilities / Threats

Newly Found Spectre Variants Bring New Concerns

Two new variants on a theme of Spectre underscore the expanding nature of the critical vulnerabilities.

The plague that is Spectre continues to evolve and adapt, showing up in two new variants this week dubbed Spectre 1.1 and Spectre 1.2 that follow the original Spectre's playbook while expanding on the ways they can do damage.

Researchers Vladimir Kiriansky of MIT and Carl Waldspurger of Carl Waldspurger Consulting discovered the new variants of the vulnerabilities in Intel microprocessors. The pair earned a $100,000 bug bounty from Intel for their responsible reporting of the new exploits, which was paid through HackerOne.

It's no surprise there are new variants on Spectre: Because of the fundamental nature of the flaw, it has been assumed that there will be a long stream of variations on the theme. The only good news on the new discoveries, says Eric Maurice, director of security assurance at Oracle in a blog post: "Fortunately, the conditions of exploitation for these issues remain similar: malicious exploitation requires the attackers to first obtain the privileges required to install and execute malicious code against the targeted systems."

Spectre 1.1

In the paper announcing the variants, Kiriansky and Waldspurger write that Spectre 1.1, "…leverages speculative stores to create speculative buffer over- flows." Unlike many of the Spectre variants that allow for threat actors to read protected memory, this buffer overflow presents the opportunity for arbitrary code execution on the affected system.

There are limits on the code execution, and the general concern is that attackers will be able to execute code that extracts data from secure memory, giving an attacker access to passwords, crypto keys, and other user authentication or data protection information.

Interestingly, the authors point out that defenses against Spectre 1.0 that use a brute-force and relatively inefficient method (a speculation barrier or lfence) would be effective against Spectre 1.1, while more efficient defenses would not.

Spectre 1.2

The second variant allows an attacker to bypass the Read/Write PTE flags if the enforcement on those flags is lax. The outcome of an exploit of this variant could ultimately allow malware to get out of a sandbox established for system security.

In many ways, Spectre 1.2 is related to Spectre 3, which is generally called Meltdown. Unfortunately, the hardware mitigations that are effective against Meltdown are not effective against Spectre 1.2.

At this time, companies including Microsoft and Red Hat say that they're looking into the new exploits to determine whether or not their products are affected. The researchers presented confirmation that both variants are effective against Intel and ARM processors.

Kiriansky and Waldspurger suggest hardware mitigations in their paper; none of the mitigations are steps that either software developers or end user organizations can take. As with the rest of the Spectre family, full mitigation is going to have to wait for a new generation of re-architected processors to emerge from vendors such as Intel and AMD.

A browser fix for a different Spectre

While the new variants were being announced, Google released a new version of the Chrome browser that mitigates some of the avenues for exploiting side-channel vulnerabilities. The Google mitigation implements what the company calls site isolation, preventing JavaScript code loaded from one website from executing on the edge device and accessing data associated with another site.

The new Chrome browser is available for Windows, Mac, Linux, and Chrome OS and makes site isolation, which had been experimental and optional, the default setting for all browsers.

Related Content:

 

 

 

Black Hat USA returns to Las Vegas with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
US Formally Attributes SolarWinds Attack to Russian Intelligence Agency
Jai Vijayan, Contributing Writer,  4/15/2021
News
Dependency Problems Increase for Open Source Components
Robert Lemos, Contributing Writer,  4/14/2021
News
FBI Operation Remotely Removes Web Shells From Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/14/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-22893
PUBLISHED: 2021-04-23
Pulse Connect Secure 9.0R3/9.1R1 and higher is vulnerable to an authentication bypass vulnerability exposed by the Windows File Share Browser and Pulse Secure Collaboration features of Pulse Connect Secure that can allow an unauthenticated user to perform remote arbitrary code execution on the Pulse...
CVE-2021-31408
PUBLISHED: 2021-04-23
Authentication.logout() helper in com.vaadin:flow-client versions 5.0.0 prior to 6.0.0 (Vaadin 18), and 6.0.0 through 6.0.4 (Vaadin 19.0.0 through 19.0.3) uses incorrect HTTP method, which, in combination with Spring Security CSRF protection, allows local attackers to access Fusion endpoints after t...
CVE-2021-31410
PUBLISHED: 2021-04-23
Overly relaxed configuration of frontend resources server in Vaadin Designer versions 4.3.0 through 4.6.3 allows remote attackers to access project sources via crafted HTTP request.
CVE-2021-31539
PUBLISHED: 2021-04-23
Wowza Streaming Engine through 4.8.5 (in a default installation) has cleartext passwords stored in the conf/admin.password file. A regular local user is able to read usernames and passwords.
CVE-2021-31540
PUBLISHED: 2021-04-23
Wowza Streaming Engine through 4.8.5 (in a default installation) has incorrect file permissions of configuration files in the conf/ directory. A regular local user is able to read and write to all the configuration files, e.g., modify the application server configuration.