Vulnerabilities / Threats

7/11/2018
06:00 PM
50%
50%

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

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
WebAuthn, FIDO2 Infuse Browsers, Platforms with Strong Authentication
John Fontana, Standards & Identity Analyst, Yubico,  9/19/2018
Turn the NIST Cybersecurity Framework into Reality: 5 Steps
Mukul Kumar & Anupam Sahai, CISO & VP of Cyber Practice and VP Product Management, Cavirin Systems,  9/20/2018
NSS Labs Files Antitrust Suit Against Symantec, CrowdStrike, ESET, AMTSO
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: "I'm not sure I like this top down management approach!"
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-17332
PUBLISHED: 2018-09-22
An issue was discovered in libsvg2 through 2012-10-19. The svgGetNextPathField function in svg_string.c returns its input pointer in certain circumstances, which might result in a memory leak caused by wasteful malloc calls.
CVE-2018-17333
PUBLISHED: 2018-09-22
An issue was discovered in libsvg2 through 2012-10-19. A stack-based buffer overflow in svgStringToLength in svg_types.c allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact because sscanf is misused.
CVE-2018-17334
PUBLISHED: 2018-09-22
An issue was discovered in libsvg2 through 2012-10-19. A stack-based buffer overflow in the svgGetNextPathField function in svg_string.c allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact because a strncpy copy limit is miscalculated.
CVE-2018-17336
PUBLISHED: 2018-09-22
UDisks 2.8.0 has a format string vulnerability in udisks_log in udiskslogging.c, allowing attackers to obtain sensitive information (stack contents), cause a denial of service (memory corruption), or possibly have unspecified other impact via a malformed filesystem label, as demonstrated by %d or %n...
CVE-2018-17321
PUBLISHED: 2018-09-22
An issue was discovered in SeaCMS 6.64. XSS exists in admin_datarelate.php via the time or maxHit parameter in a dorandomset action.