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.

Security Management //

Patch Management

6/15/2018
08:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Intel Chips' 'Lazy FP' Vulnerability Could Leak Secure Data

A group of security researchers have found a new vulnerability with Intel's chips that can theoretically allow an attack to utilize the 'Lazy FP' state of the process and gain access to sensitive data.

Intel is warning that the Spectre and Meltdown variant 3A exploit will allow a program to obtain scraps of the Floating Point Unit (FPU) context of another app on Intel Core and Xeon processors.

The tracking number for this is CVE-2018-3665.

This "moderate" security problem happens because system software can utilize what is called "the Lazy FP state restore technique" to delay the restoring of state until an instruction operating on that state is actually executed by the new process. This may allow a local process to infer data utilizing Lazy FP state restore from another process through a speculative execution side channel.

Intel recommends system software developers utilize the "Eager FP state restore" in lieu of Lazy FP state restore. This includes:

  • Modern Linux: Going from kernel version 4.9, which was released in 2016
  • Windows: Including Windows Server 2016
  • Other Kernels: Including OpenSD and DragonflyBSD, which already use this technique routinely

(Source: Flickr)
(Source: Flickr)

Windows Server 2008 will need a patch, and the Linux kernel team is said to be back-porting mitigations to pre-4.9 kernels.

These techniques do not carry a performance hit. It has been found that eager state switching can even increase performance.

This kind of vulnerability -- though there are no known exploits in the wild at this time --could compromise cryptographic keys that are used to secure data in the system. Crypto programs routinely utilize the FPU to carry out the mathematical operations needed for cryptography.

Other external programs, such as malware, might be able to obtain or guess parts of these cryptographic keys by examining the state of the FPU.

Intel credited Julian Stecklina from Amazon Germany; Thomas Prescher from Cyberus Technology GmbH; Zdenek Sojka from SYSGO AG; as well as researcher Colin Perceiver, for bringing this latest side-channel vulnerability to light.

It has also been reported that Google found that its systems are secured against the lazy FPU state restore.


Now entering its fifth year, the 2020 Vision Executive Summit is an exclusive meeting of global CSP executives focused on navigating the disruptive forces at work in telecom today. Join us in Lisbon on December 4-6 to meet with fellow experts as we define the future of next-gen communications and how to make it profitable.

Red Hat Linux also addressed the problem. The open source company notes, "RHEL-7 will automatically default to (safe) 'eager' floating point register restore on Sandy Bridge and newer Intel processors. AMD processors are not affected."

The company also say that users can mitigate this issue on older processors in RHEL 7 by booting the kernel with the "eagerfpu=on" parameter to enable eager FPU restore mode.

RHEL 6 and earlier versions are affected by the problem, but Red Hat says it will be releasing updates that will fix it.

It's also been reported by the Register that the announcement of the vulnerability was supposed to occur on June 27, but the BSD teams issued an early mitigation fix after Intel declined to work with them under embargo. This forced Intel to go public earlier than it had planned.

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
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-42258
PUBLISHED: 2021-10-22
BQE BillQuick Web Suite 2018 through 2021 before 22.0.9.1 allows SQL injection for unauthenticated remote code execution, as exploited in the wild in October 2021 for ransomware installation. SQL injection can, for example, use the txtID (aka username) parameter. Successful exploitation can include ...
CVE-2020-28968
PUBLISHED: 2021-10-22
Draytek VigorAP 1000C contains a stored cross-site scripting (XSS) vulnerability in the RADIUS Setting - RADIUS Server Configuration module. This vulnerability allows attackers to execute arbitrary web scripts or HTML via a crafted payload in the username input field.
CVE-2020-28969
PUBLISHED: 2021-10-22
Aplioxio PDF ShapingUp 5.0.0.139 contains a buffer overflow which allows attackers to cause a denial of service (DoS) via a crafted PDF file.
CVE-2020-36485
PUBLISHED: 2021-10-22
Portable Ltd Playable v9.18 was discovered to contain an arbitrary file upload vulnerability in the filename parameter of the upload module. This vulnerability allows attackers to execute arbitrary code via a crafted JPEG file.
CVE-2020-36486
PUBLISHED: 2021-10-22
Swift File Transfer Mobile v1.1.2 and below was discovered to contain a cross-site scripting (XSS) vulnerability via the 'path' parameter of the 'list' and 'download' exception-handling.