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

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
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 Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20001
PUBLISHED: 2020-08-04
An issue was discovered in RICOH Streamline NX Client Tool and RICOH Streamline NX PC Client that allows attackers to escalate local privileges.
CVE-2020-15467
PUBLISHED: 2020-08-04
The administrative interface of Cohesive Networks vns3:vpn appliances before version 4.11.1 is vulnerable to authenticated remote code execution leading to server compromise.
CVE-2020-5615
PUBLISHED: 2020-08-04
Cross-site request forgery (CSRF) vulnerability in [Calendar01] free edition ver1.0.0 and [Calendar02] free edition ver1.0.0 allows remote attackers to hijack the authentication of administrators via unspecified vectors.
CVE-2020-5616
PUBLISHED: 2020-08-04
[Calendar01], [Calendar02], [PKOBO-News01], [PKOBO-vote01], [Telop01], [Gallery01], [CalendarForm01], and [Link01] [Calendar01] free edition ver1.0.0, [Calendar02] free edition ver1.0.0, [PKOBO-News01] free edition ver1.0.3 and earlier, [PKOBO-vote01] free edition ver1.0.1 and earlier, [Telop01] fre...
CVE-2020-5617
PUBLISHED: 2020-08-04
Privilege escalation vulnerability in SKYSEA Client View Ver.12.200.12n to 15.210.05f allows an attacker to obtain unauthorized privileges and modify/obtain sensitive information or perform unintended operations via unspecified vectors.