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.

Application Security //

Ransomware

3/5/2019
06:00 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Boosted Rowhammer & Cache Attacks Spell Bad News for Intel

Researchers from Worcester Polytechnic Institute in Massachusetts and the University of Lubeck in Germany have published a paper that is really bad news for Intel.

Researchers from Worcester Polytechnic Institute in Massachusetts and the University of Lübeck in Germany have published a paper, "SPOILER: Speculative Load Hazards Boost Rowhammer and Cache Attacks," that is really bad news for Intel.

It outlines an attack similar to that of Spectre and Meltdown in that it is based the results of speculative execution in a CPU, but on a different set of registers than the first ones use. Here, the Memory Order Buffer is targeted. The MOB is coupled with a CPU cache to manage memory operations.

The researchers found that only Intel CPU chips are vulnerable to this attack. Arm and AMD CPUs are not affected.

The dependency resolution logic that serves the speculative load in the CPU can be exploited to gain information about the physical page mappings that are associated with that load. This is what Rowhammer and cache attacks do in order to obtain a reverse engineering of the virtual-to-physical address mapping.

Worse for Intel, they improved the Rowhammer attack by showing how SPOILER -- the name they gave this class of attack -- helps to conduct DRAM row conflicts deterministically with up to 100% chance, and by demonstrating a double-sided Rowhammer attack with normal user's privilege.

Intel uses a proprietary memory disambiguation and dependency resolution logic in the processors to predict and resolve false dependencies that are related to the speculative load. This makes the speculation results happen faster by not wasting time on intermediate results.

The researchers discovered a false dependency in this process that happens during the 1 MB aliasing of speculative memory accesses which is exploited to leak information about physical page mappings. They note in their paper that, "The leakage can be exploited by a limited set of instructions, which is visible in all Intel generations starting from the1st generation of Intel Core processors, independent of the OS and also works from within virtual machines and sandboxed environments."

So, the root cause for SPOILER is a weakness in the address speculation of Intel's proprietary implementation of the memory subsystem which directly leaks timing behavior due to physical address conflicts.

Oh man, that is a total loss for Intel.

It will make Rowhammer and cache attacks easier, as well as making JavaScript-enabled attacks more feasible.

Mitigation solutions already worked out for Spectre and Meltdown won't work for SPOILER, even though they are both side-channel types of attacks.

The researchers also state that, "There is no software mitigation that can completely erase this problem... The hardware design for the memory disambiguator may be revised to prevent such physical address leakage, but modifying the speculative behavior may cause performance impacts. For instance, partial address comparison was a design choice for performance. Full address comparison may address this vulnerability, but will also impact performance."

Intel is not panicking yet. In a prepared statement given to The Register, they said, "Intel received notice of this research, and we expect that software can be protected against such issues by employing side channel safe software development practices. This includes avoiding control flows that are dependent on the data of interest. We likewise expect that DRAM modules mitigated against Rowhammer style attacks remain protected."

This isn't done yet, not by a long shot.

— 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/25/2020
9 Tips to Prepare for the Future of Cloud & Network Security
Kelly Sheridan, Staff Editor, Dark Reading,  9/28/2020
Attacker Dwell Time: Ransomware's Most Important Metric
Ricardo Villadiego, Founder and CEO of Lumu,  9/30/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-2019-20902
PUBLISHED: 2020-10-01
Upgrading Crowd via XML Data Transfer can reactivate a disabled user from OpenLDAP. The affected versions are from before version 3.4.6 and from 3.5.0 before 3.5.1.
CVE-2019-20903
PUBLISHED: 2020-10-01
The hyperlinks functionality in atlaskit/editor-core in before version 113.1.5 allows remote attackers to inject arbitrary HTML or JavaScript via a Cross-Site Scripting (XSS) vulnerability in link targets.
CVE-2020-25288
PUBLISHED: 2020-09-30
An issue was discovered in MantisBT before 2.24.3. When editing an Issue in a Project where a Custom Field with a crafted Regular Expression property is used, improper escaping of the corresponding form input's pattern attribute allows HTML injection and, if CSP settings permit, execution of arbitra...
CVE-2020-25781
PUBLISHED: 2020-09-30
An issue was discovered in file_download.php in MantisBT before 2.24.3. Users without access to view private issue notes are able to download the (supposedly private) attachments linked to these notes by accessing the corresponding file download URL directly.
CVE-2020-25830
PUBLISHED: 2020-09-30
An issue was discovered in MantisBT before 2.24.3. Improper escaping of a custom field's name allows an attacker to inject HTML and, if CSP settings permit, achieve execution of arbitrary JavaScript when attempting to update said custom field via bug_actiongroup_page.php.