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

1/30/2020
10:00 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

All Your Intel L1 Cache Belongs to CacheOut

Once again, a novel 'speculative execution side-channel' attack has been discovered by researchers.

Once again, a novel "speculative execution side-channel" attack has been discovered by researchers. They show in their paper on the attackthat it will work against modern Intel microprocessors.

Intel refers to the vulnerability as L1D Eviction Sampling, since it can enable an attacker to read from the CPU's Level 1 Data Cache. CacheOut/L1D can leak information from other processes running on the same thread, or across threads on the same CPU core.

The attack has been given the moniker of "CacheOut" by the researchers and there is a snappy website with logo that is devoted to it. As of yet, there have been no signs of this style of attack in the wild. CVE-2020-0549 has been assigned to it, with a CVSS score of 6.5 (Medium). The need for an attacker to have local access to the target for the exploit to succeed no doubt contributed to the lowering of the severity score.

The researchers say that the AMD line of microprocessors is not affected by CacheOut, since AMD does not offer any feature similar to Intel's Transactional Synchronization Extensions (TSX). TSX is there so the processor can guarantee that the instructions that form a transaction either all execute to completion or none of them will execute at all.

Arm and IBM do have a feature similar to Intel TSX, but the researchers are currently unaware of whether any of their products are affected. They are also unaware of any other attack vectors to exploit CacheOut.

The extent of the vulnerability extends across the entire chip architecture. CacheOut exploits the hardware vulnerabilities that were uncovered to dump the contents of Intel Security Guard Extensions (SGX) enclaves, for example. As such, any information stored inside the enclave can be potentially leaked by CacheOut. That's not supposed to be happening.

There are no data trails left after exploitation, as well. CacheOut does not leave any traces in traditional log files.

Virtual machines are also vulnerable to this. CacheOut exploits hardware security vulnerabilities inside the processor to leak information from both the virtual machine manager (hypervisor) and co-resident virtual machines, which is one of the things that the use of SGX was supposed to prevent.

The techniques recommended by Intel to mitigate previous similar attacks (ZombleLoad, for example) don't work in this case. This mitigation is incomplete, as the researchers showed that they can force the victim's data out of the L1-D Cache into the microarchitectural buffers after the operating system clears them. They showed that they could subsequently leak the contents of the buffers and obtain the victim's data.

Intel says it is working on microcode patches to fix the vulnerability. But the open question is how much these sort of patches -- when they come -- will affect the overall performance of the microprocessor.

— 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
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Enterprises are Attacking the Cybersecurity Problem
Concerns over supply chain vulnerabilities and attack visibility drove some significant changes in enterprise cybersecurity strategies over the past year. Dark Reading's 2021 Strategic Security Survey showed that many organizations are staying the course regarding the use of a mix of attack prevention and threat detection technologies and practices for dealing with cyber threats.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-0652
PUBLISHED: 2021-10-22
In VectorDrawable::VectorDrawable of VectorDrawable.java, there is a possible way to introduce a memory corruption due to sharing of not thread-safe objects. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitati...
CVE-2021-0702
PUBLISHED: 2021-10-22
In RevertActiveSessions of apexd.cpp, there is a possible way to share the wrong file due to an unintentional MediaStore downgrade. This could lead to local information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: An...
CVE-2021-0703
PUBLISHED: 2021-10-22
In SecondStageMain of init.cpp, there is a possible use after free due to incorrect shared_ptr usage. This could lead to local escalation of privilege if the attacker has physical access to the device, with no additional execution privileges needed. User interaction is not needed for exploitation.Pr...
CVE-2021-0705
PUBLISHED: 2021-10-22
In sanitizeSbn of NotificationManagerService.java, there is a possible way to keep service running in foreground and keep granted permissions due to Bypass of Background Service Restrictions. This could lead to local escalation of privilege with no additional execution privileges needed. User intera...
CVE-2021-0706
PUBLISHED: 2021-10-22
In startListening of PluginManagerImpl.java, there is a possible way to disable arbitrary app components due to a missing permission check. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersi...