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
News
FluBot Malware's Rapid Spread May Soon Hit US Phones
Kelly Sheridan, Staff Editor, Dark Reading,  4/28/2021
Slideshows
7 Modern-Day Cybersecurity Realities
Steve Zurier, Contributing Writer,  4/30/2021
Commentary
How to Secure Employees' Home Wi-Fi Networks
Bert Kashyap, CEO and Co-Founder at SecureW2,  4/28/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27941
PUBLISHED: 2021-05-06
Unconstrained Web access to the device's private encryption key in the QR code pairing mode in the eWeLink mobile application (through 4.9.2 on Android and through 4.9.1 on iOS) allows a physically proximate attacker to eavesdrop on Wi-Fi credentials and other sensitive information by monitoring the...
CVE-2021-29203
PUBLISHED: 2021-05-06
A security vulnerability has been identified in the HPE Edgeline Infrastructure Manager, also known as HPE Edgeline Infrastructure Management Software, prior to version 1.22. The vulnerability could be remotely exploited to bypass remote authentication leading to execution of arbitrary commands, gai...
CVE-2021-31737
PUBLISHED: 2021-05-06
emlog v5.3.1 and emlog v6.0.0 have a Remote Code Execution vulnerability due to upload of database backup file in admin/data.php.
CVE-2020-28198
PUBLISHED: 2021-05-06
** UNSUPPORTED WHEN ASSIGNED ** The 'id' parameter of IBM Tivoli Storage Manager Version 5 Release 2 (Command Line Administrative Interface, dsmadmc.exe) is vulnerable to an exploitable stack buffer overflow. Note: the vulnerability can be exploited when it is used in "interactive" mode wh...
CVE-2021-28665
PUBLISHED: 2021-05-06
Stormshield SNS with versions before 3.7.18, 3.11.6 and 4.1.6 has a memory-management defect in the SNMP plugin that can lead to excessive consumption of memory and CPU resources, and possibly a denial of service.