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.

Vulnerabilities / Threats

12/10/2019
02:00 PM
Irfan Ahmed
Irfan Ahmed
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

Intel's CPU Flaws Continue to Create Problems for the Tech Community

We can't wait out this problem and hope that it goes away. We must be proactive.

The tech community was once again blindsided with news last month of another security exploit involving Intel's processors; exploits have continued to be discovered since Meltdown and Spectre were first unveiled two years ago, causing widespread concern about the ramifications for computer systems globally. In addition to leaving sensitive data exposed, the vulnerabilities also put businesses in the difficult, but necessary, position of implementing mitigations that can seriously reduce the performance of computers and servers.

In January 2018, researchers revealed two exploits that take advantage of side-channel vulnerabilities found in computer chips manufactured since the mid-1990s. Since that time, six additional exploits — Foreshadow ZombieloadRIDLFallout, SWAPGS, and now TAA  — have been discovered that take advantage of the same vulnerabilities. While chips made by AMD and ARM are affected to a minimal degree, the vast majority of Intel's chips are affected by all of these exploits. And due to Intel's dominant market position, this vulnerability can be found in nearly every computer on the planet.

These exploits take advantage of a process called "speculative execution," a process introduced in the 1990s by Intel and other chipmakers as they sought to increase the speed of computer processors. In short, computer processors can "speculate" (or guess) what a user will run next, increasing speed by not having to wait to execute actions until they are formally received. While this process was credited with significantly improving the speed of computers, the exploits are able to give unauthorized users access to what should be confidential data, creating a vast security vulnerability. They typically leak data from different internal CPU buffers such as line-fill buffers, load ports, and store buffers.

To address this problem, Intel has provided software patches or businesses can apply other workarounds, such as disabling hyper-threading technology in vulnerable computers. However, both of these fixes can reduce the performance of CPUs. LoginVSI recently released a survey of IT professionals regarding the impact of the patches and found that approximately 20% of them experienced performance reductions of up to 10% on their systems, and another 11% said they experienced a performance hit up to 15%. Some respondents had performance impacts as high as 20%.

While addressing this problem is challenging, what is clear, as noted recently by a leading Linux developer, is that the security problems with Intel's chips "are not going away." So, we cannot simply wait this problem out and hope that it disappears. We must be proactive.

To understand the extent of the risk, the first thing any business should do is conduct an audit of the CPUs that it has in its systems. The easiest approach would then be to replace all affected CPUs with unaffected hardware. However, replacing all affected hardware may very well be cost-prohibitive.

Therefore, businesses should begin immediately diversifying and randomizing their CPUs. It can do this by purchasing unaffected chips (for example, from AMD) as it goes through its normal upgrade cycles and then randomizing affected Intel chips across its systems, strategically placing them in servers and computers where they are least vulnerable to hacks. In addition, by placing the affected CPUs in areas with lighter workloads, a business can also reduce the overall effect of the performance reductions caused by the software patches.

It would also be prudent to hire experienced IT security staff, plan for the increased energy costs of running current systems at maximum for longer periods of time to offset the performance reductions of the patches, or identify revenue streams to purchase new servers to add processing capacity.

While it is clear that being insecure is not a practical option, businesses must remember that there is not a one-size-fits-all solution. A company's remedies to this ongoing challenge must be assessed within the context of its own unique and dynamic technology environment. Undoubtedly, this challenge will be expensive, burdensome, and time consuming for businesses.

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "Criminals Hide Fraud Behind the Green Lock Icon."

Irfan Ahmed is an Assistant Professor in the Department of Computer Science at Virginia Commonwealth University (VCU), where he runs the Security and Forensics Engineering (SAFE) Lab. His research interests include system security, malware, digital forensics, and industrial ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Waleedbaig1
50%
50%
Waleedbaig1,
User Rank: Apprentice
12/11/2019 | 10:43:27 PM
Is the risk really reduce by this suggested approach ?
In a production environment, Having a mix of intel processors (vulnerable) and other vendors processors will certainly reduce the liklhood of the breach but overall impact will remain same. Any thought ?
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Inside North Korea's Rapid Evolution to Cyber Superpower
Kelly Sheridan, Staff Editor, Dark Reading,  12/1/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
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
Assessing Cybersecurity Risk in Todays Enterprises
Assessing Cybersecurity Risk in Todays 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-25465
PUBLISHED: 2020-12-04
Null Pointer Dereference. in xObjectBindingFromExpression at moddable/xs/sources/xsSyntaxical.c:3419 in Moddable SDK before OS200908 causes a denial of service (SEGV).
CVE-2020-25461
PUBLISHED: 2020-12-04
Invalid Memory Access in the fxProxyGetter function in moddable/xs/sources/xsProxy.c in Moddable SDK before OS200908 causes a denial of service (SEGV).
CVE-2020-25462
PUBLISHED: 2020-12-04
Heap buffer overflow in the fxCheckArrowFunction function at moddable/xs/sources/xsSyntaxical.c:3562 in Moddable SDK before OS200903.
CVE-2020-25463
PUBLISHED: 2020-12-04
Invalid Memory Access in fxUTF8Decode at moddable/xs/sources/xsCommon.c:916 in Moddable SDK before OS200908 causes a denial of service (SEGV).
CVE-2020-25464
PUBLISHED: 2020-12-04
Heap buffer overflow at moddable/xs/sources/xsDebug.c in Moddable SDK before before 20200903. The top stack frame is only partially initialized because the stack overflowed while creating the frame. This leads to a crash in the code sending the stack frame to the debugger.