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.

Infrastructure Security

1/3/2018
02:00 PM
Curtis Franklin
Curtis Franklin
Curt Franklin
50%
50%

New Intel Vulnerability Hits Almost Everyone

A vulnerability in the way that Intel CPUs deal with memory could leave everyone using an Intel-based computer open to attack.

News is breaking about a massive vulnerability in Intel CPUs -- a vulnerability that could potentially allow hackers to gain access to protected system memory holding encryption keys, authentication details and other goodies. Happy New Year.

Normally, each process running on an Intel CPU has its own address space. The system has an address space separate from all of the process address spaces. In normal operation, processes may be able to see parts of the kernel address space to complete necessary operations, but they can't change data in the kernel space. And the ability for a process to see into the kernel space is carefully controlled for both security and system stability reasons.

Because of the flaw, first recognized by a research group from Graz University of Technology, Austria, obliquely discussed in a paper titled KASLR is DEAD: Long Live KASLR, [Author's Note: KASLR is Kernel Address Space Layout Randomization, a technique that increases security by frequently moving kernel addresses around.] the separation between the user (process) space and kernel space can become very porous. And then it gets worse.

Modern Intel CPUs boost performance by trying to anticipate what processes will need, essentially pre-executing commands to make data available as quickly as possible. By carefully manipulating these commands executed ahead of time, a hacker can gain access to the contents of kernel memory that they shouldn't be allowed to see. And then it gets worse.

The first step down the path toward "worse" is ubiquity: It doesn't matter which operating system you're using -- it's going to have to be patched in order to deal with this vulnerability. This is the rare case in which Linux users can't be smug, nor can MacOS users or Windows users. And those who keep their systems rigorously updated are no safer than those still running a decade-old system. In the words of REM, "Everybody hurts."

Now, there's a glimmer of good news, in that the OS can be patched to shut off the technology that leads to the vulnerability, but that medicine comes with a foul side-effect: Your patched systems will be slower. How much slower? Depending on precisely which applications and processes you're running, anywhere from 20% to 33% slower. Let that sink in for a moment.

The only people who don't have to worry at all about this vulnerability are those running systems powered by AMD processors, because they do things differently when it comes to memory page table isolation and speculative operations/data references. Of course, AMD processors have had their own security issues in the past, so those system owners should probably be a bit circumspect in their gloating.

For those keeping score, this vulnerability exploit is similar in many ways to the rowhammer bug used to gain access to the contents of DRAM. It's likely that we will see more of these hardware-based exploits as operating system and application programmers get better at testing and correcting flaws before they hit general availability.

This story is going to continue to develop, so stay tuned to us here at Security Now. And let us know if you hear any news about this flaw, especially if you hear reliable information on exploits beyond the current proof-of-concept attacks seen so far.

Welcome to 2018 and fasten your seatbelts -- it's going to be a rocky year.

Related posts:

— Curtis Franklin is the editor of SecurityNow.com. Follow him on Twitter @kg4gwa.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Digital Clones Could Cause Problems for Identity Systems
Robert Lemos, Contributing Writer,  8/8/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
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
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-8913
PUBLISHED: 2020-08-12
A local, arbitrary code execution vulnerability exists in the SplitCompat.install endpoint in Android's Play Core Library versions prior to 1.7.2. A malicious attacker could create an apk which targets a specific application, and if a victim were to install this apk, the attacker could perform a dir...
CVE-2020-7029
PUBLISHED: 2020-08-11
A Cross-Site Request Forgery (CSRF) vulnerability was discovered in the System Management Interface Web component of Avaya Aura Communication Manager and Avaya Aura Messaging. This vulnerability could allow an unauthenticated remote attacker to perform Web administration actions with the privileged ...
CVE-2020-17489
PUBLISHED: 2020-08-11
An issue was discovered in certain configurations of GNOME gnome-shell through 3.36.4. When logging out of an account, the password box from the login dialog reappears with the password still visible. If the user had decided to have the password shown in cleartext at login time, it is then visible f...
CVE-2020-17495
PUBLISHED: 2020-08-11
django-celery-results through 1.2.1 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database.
CVE-2020-0260
PUBLISHED: 2020-08-11
There is a possible out of bounds read due to an incorrect bounds check.Product: AndroidVersions: Android SoCAndroid ID: A-152225183