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.

Cloud Security //

Google

8/20/2018
09:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Foreshadow-NG Vulnerability Sets Tech Giants Scrambling

Foreshadow vulnerabilities expose processors and even the cloud to penetration.

In early January, the Spectre and Meltdown vulnerabilities were disclosed to the computer world, which promptly lost its shirt for a period. This was a new class of attacks that depended on the way that modern processors shoved data in and out of the CPU, a process that was never thought to be problematic.

Eventually, patches and mitigations for these potential attacks were developed and installed. A sigh of relief arose from everyone in the field.

But everyone was wrong. The problem was more complex and destructive than it appeared.

It turns out that when Spectre was announced, some other researchers (two teams of them, actually) found that the problem was much deeper than it seemed. It went deep enough to threaten the supposedly secure data enclaves on the chip (Intel calls it SGX) that were there to stop one part of memory from accessing another more secure part of the same memory.

The researchers call the hole “Foreshadow.” This kind of SGX access was previously thought not to be possible in the Spectre and Meltdown problems.

Wait, it gets worse.

Source: Christopher Burns via Unsplash
Source: Christopher Burns via Unsplash

As Intel looked deeper, they realized this was bigger than just SGX. Intel and that second team found a variant of the original attack dubbed Foreshadow-Next Generation (NG) (PDF) that could expose information stored in the processor’s L1 cache (the one that is architecturally closest to the activity in the CPU), as well as information associated with the SMM, the operating system’s kernel, and hypervisors. It could also affect processors besides those of Intel.

So, there are multiple problems that have been admitted by Intel.

There is CVE-2018-3615 (the original SGX one), CVE-2018-3620, that opens up operating systems and System Management Mode (SMM), and CVE-2018-3646 affecting virtualization software and Virtual Machine Monitors (VMM).

Intel thinks that, taken together, the impact is huge. The company summarizes what it thinks in four points:

  1. Malicious applications may be able to infer the values of data in the operating system memory or data from other applications.
  2. A malicious guest virtual machine (VM) may be able to infer the values of data in the VMM’s memory or values of data in the memory of other guest VMs.
  3. Malicious software running outside of SMM may be able to infer values of data in SMM memory.
  4. Malicious software running outside of an SGX enclave or within an enclave may be able to infer data from within another SGX enclave.

If you let that sink it, it means that virtual machines -- the kind that run in the cloud -- are at risk.

Not only that, but the microcode updates that Intel has done to mitigate will not be enough by itself. The OS as well as the hypervisor controlling those cloud machines will need to be patched or updated.

Boy howdy, this is now some big-time aggravation.

Microsoft has an advisory out there that speaks about the way it is plugging holes in Azure. Google also says it’s doing the same for its cloud, as does Amazon for AWS.

Software vendors are also scrambling to patch their software to reflect this situation.

The true solution is going to require new CPU hardware that does things differently, not just some kludge that protects against known attacks. Those CPUs may be under development, as Intel says, but they’re not here yet.

Related posts:

— 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
Threaded  |  Newest First  |  Oldest First
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...