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

5/23/2018
08:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Spectre Number 4 Disclosure Raises Fresh Hardware Alarms

The latest side-channel vulnerability, dubbed Spectre Number 4, is raising new alarms about widespread issues in chips, beyond x86. However, this time, Intel is trying a different approach.

If you were waiting for the Spectre vulnerabilities to abate, there's a problem -- another variant of the side channel attack is out there. And the patch Intel has let loose for it will decrease CPU performance by around 8%.

This variant -- CVE-2018-3639 or "Spectre Number 4," as it's commonly called -- depends on Spectre-like speculative execution, as well as speculative execution of memory reads before the addresses of all prior memory writes are known. (Yes, this is très geeky.)

With a technique called side-channel analysis, a local user can then figure out data residing on the machine.

The researchers demonstrated Variant 4 in a language-based runtime environment. While Intel is not aware of a successful browser exploit, the most common use of runtimes, such as JavaScript, is in web browsers.

The variant works on x86 chips, including Intel and AMD chipsets, as well as IBM's Power 8, Power 9 and System Z mainframes. It also appears to affect ARM chips as well, too.

So this is not an Intel-only problem.

Intel has published a description of the vulnerability in its "Q2 2018 Speculative Execution Side Channel Update." The chip maker calls it the Speculative Store Bypass (SSB) variant and assign a Medium severity to it.

But, in a change for Intel, the company is addressing the problem heads-on and what mitigation its solution will bring.

While the beta patch the company has delivered will have no performance hit in the default off configuration, Intel did note that: "If enabled, we've observed a performance impact of approximately 2 to 8 percent based on overall scores for benchmarks like SYSmark® 2014 SE and SPEC integer rate on client1 and server2 test systems."

Gartner analyst Neil MacDonald thinks that the security community should pay attention to this.

"The security community needs to care about these latest announcements for three reasons," McDonald told Security Now, adding:

First, yet another round of microcode updates will be required to remediate them and these have proven to be the most difficult to roll out. Second, even though the severity is rated medium, we are going to want to address these using a structured, risk-based approach and ultimately apply the OS, VMM and microcode updates. There is no need to panic, but we shouldn't leave these systems unpatched forever unless there is no other option or if the risk of arbitrary code execution is near zero (this is certainly not true on most end user systems). Third, as we expected this is just the latest in what were expect will be a number of new ways to attack the underlying vulnerable design implementation. We are only at the beginning of Spectre/Meltdown class attacks. Expect more patches and firmware updates over the next 12-18 months as researchers and attackers continue to try out new attack methods.

MacDonald thinks we aren't done yet in this cycle, and we may not be. But the security community is going to have to decide when the hardware has been sufficiently hardened to be routinely usable.

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
NSA Appoints Rob Joyce as Cyber Director
Dark Reading Staff 1/15/2021
Vulnerability Management Has a Data Problem
Tal Morgenstern, Co-Founder & Chief Product Officer, Vulcan Cyber,  1/14/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-20949
PUBLISHED: 2021-01-20
Bleichenbacher's attack on PKCS #1 v1.5 padding for RSA in STM32 cryptographic firmware library software expansion for STM32Cube (UM1924). The vulnerability can allow one to use Bleichenbacher's oracle attack to decrypt an encrypted ciphertext by making successive queries to the server using the vul...
CVE-2020-25683
PUBLISHED: 2021-01-20
A flaw was found in dnsmasq before version 2.83. A heap-based buffer overflow was discovered in dnsmasq when DNSSEC is enabled and before it validates the received DNS entries. A remote attacker, who can create valid DNS replies, could use this flaw to cause an overflow in a heap-allocated memory. T...
CVE-2020-25684
PUBLISHED: 2021-01-20
A flaw was found in dnsmasq before version 2.83. When getting a reply from a forwarded query, dnsmasq checks in the forward.c:reply_query() if the reply destination address/port is used by the pending forwarded queries. However, it does not use the address/port to retrieve the exact forwarded query,...
CVE-2020-25685
PUBLISHED: 2021-01-20
A flaw was found in dnsmasq before version 2.83. When getting a reply from a forwarded query, dnsmasq checks in forward.c:reply_query(), which is the forwarded query that matches the reply, by only using a weak hash of the query name. Due to the weak hash (CRC32 when dnsmasq is compiled without DNSS...
CVE-2020-35271
PUBLISHED: 2021-01-20
Employee Performance Evaluation System in PHP/MySQLi with Source Code 1.0 is affected by cross-site scripting (XSS) in the Employees, First Name and Last Name fields.