Endpoint

7/13/2018
01:20 PM
Connect Directly
Twitter
Twitter
RSS
E-Mail
50%
50%

8 Big Processor Vulnerabilities in 2018

Security researchers have been working in overdrive examining processors for issues - and they haven't come up empty-handed.
Previous
1 of 9
Next

Image Source: Adobe Stock (Shawn)

Image Source: Adobe Stock (Shawn)

Since the Spectre and Meltdown vulnerabilities knocked the glow off of the new year, 2018 has been the year of the CPU bug. Security researchers have been working in overdrive examining processors for design flaws, firmware bugs, and other vulnerabilities that put an entire computing architecture at risk.

They haven't come up empty-handed.

Here's what we've had to contend with this year on the CPU vulnerability front — and what we can expect in a couple of weeks when new research hits the stage at Black Hat.

 

 

 

Black Hat USA returns to Las Vegas with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

 

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Previous
1 of 9
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
tomas.honzak@gooddata.com
100%
0%
[email protected],
User Rank: Author
7/17/2018 | 3:02:32 PM
Excellent overview -- but does it end here?
Nicely summarized the evolution of the biggest hardware-level nightmare of 2018 (I hope I don't have to include "so far"...) 

After spending a good part of this year watching our infrastructure engineers and security experts trying to come up with a solid mitigation plan that would not kill our SaaS platform immediately and seeing how our response strategy had to change more than a dozen times as the new and updated kernel patches and CPU microcodes were published and recalled, and new and updated attack vectors and vulnerabilities were discovered, it became literally impossible to keep track of our overall exposure and risks.

Not to mention our enterprise customers, who tried so hard to keep track on our patching progress for the first three months of the year, after which they gave up as the development of this crisis turned into an unmanageable nightmare.

In the end, similarly to how the industry seems to be getting used to the fact that data breaches are the new reality and the overwhelming amount of new incidents does not come out as a surprise anymore, we need to accept that the complexity of today's CPUs, together with the fact that the primary focus of the manufacturers was, is and will be the performance, means that there might be many additional hw-level security flaws to be discovered over the next months and years.

To me, the takeaway is very simple: security and privacy are ongoing end to end process and rather than relying on particular technology or safeguard, we need to continue looking on risks and mitigate them on all the levels, starting by collecting just the minimal data needed - and ending by continuously improving the layered security.
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security 2018
This Dark Reading Tech Digest explores the biggest news stories of 2018 that shaped the cybersecurity landscape.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-3906
PUBLISHED: 2019-01-18
Premisys Identicard version 3.1.190 contains hardcoded credentials in the WCF service on port 9003. An authenticated remote attacker can use these credentials to access the badge system database and modify its contents.
CVE-2019-3907
PUBLISHED: 2019-01-18
Premisys Identicard version 3.1.190 stores user credentials and other sensitive information with a known weak encryption method (MD5 hash of a salt and password).
CVE-2019-3908
PUBLISHED: 2019-01-18
Premisys Identicard version 3.1.190 stores backup files as encrypted zip files. The password to the zip is hard-coded and unchangeable. An attacker with access to these backups can decrypt them and obtain sensitive data.
CVE-2019-3909
PUBLISHED: 2019-01-18
Premisys Identicard version 3.1.190 database uses default credentials. Users are unable to change the credentials without vendor intervention.
CVE-2019-3910
PUBLISHED: 2019-01-18
Crestron AM-100 before firmware version 1.6.0.2 contains an authentication bypass in the web interface's return.cgi script. Unauthenticated remote users can use the bypass to access some administrator functionality such as configuring update sources and rebooting the device.