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.

Endpoint

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

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.
2 of 9

Spectre and Meltdown
Before the haze from New Year's Eve fireworks even had a chance to dissipate, the security world was rocked by the disclosure of Spectre and Meltdown, two similar side-channel flaws in CPUs from Intel, AMD, and ARM. Affecting nearly all modern microprocessors, the vulnerabilities were found in how they carry out the functions of caching and speculative execution. The latter is particularly depended on to optimize CPU performance by predicting a command before it is even requested. These vulnerabilities can be exploited to force the operating system and applications to expose system memory data, which could include any nature of protected information, such as passwords and encryption keys.
Image Source: Adobe Stock (Production Perig)

Spectre and Meltdown

Before the haze from New Year's Eve fireworks even had a chance to dissipate, the security world was rocked by the disclosure of Spectre and Meltdown, two similar side-channel flaws in CPUs from Intel, AMD, and ARM. Affecting nearly all modern microprocessors, the vulnerabilities were found in how they carry out the functions of caching and speculative execution. The latter is particularly depended on to optimize CPU performance by predicting a command before it is even requested. These vulnerabilities can be exploited to force the operating system and applications to expose system memory data, which could include any nature of protected information, such as passwords and encryption keys.

Image Source: Adobe Stock (Production Perig)

2 of 9
Comment  | 
Print  | 
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.
A Realistic Threat Model for the Masses
Lysa Myers, Security Researcher, ESET,  10/9/2019
USB Drive Security Still Lags
Dark Reading Staff 10/9/2019
Virginia a Hot Spot For Cybersecurity Jobs
Jai Vijayan, Contributing Writer,  10/9/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-17612
PUBLISHED: 2019-10-15
An issue was discovered in 74CMS v5.2.8. There is a SQL Injection generated by the _list method in the Common/Controller/BackendController.class.php file via the index.php?m=Admin&c=Ad&a=category sort parameter.
CVE-2019-17613
PUBLISHED: 2019-10-15
qibosoft 7 allows remote code execution because do/jf.php makes eval calls. The attacker can use the Point Introduction Management feature to supply PHP code to be evaluated. Alternatively, the attacker can access admin/index.php?lfj=jfadmin&action=addjf via CSRF, as demonstrated by a payload in...
CVE-2019-17395
PUBLISHED: 2019-10-15
In the Rapid Gator application 0.7.1 for Android, the username and password are stored in the log during authentication, and may be available to attackers via logcat.
CVE-2019-17602
PUBLISHED: 2019-10-15
An issue was discovered in Zoho ManageEngine OpManager before 12.4 build 124089. The OPMDeviceDetailsServlet servlet is prone to SQL injection. Depending on the configuration, this vulnerability could be exploited unauthenticated or authenticated.
CVE-2019-17394
PUBLISHED: 2019-10-15
In the Seesaw Parent and Family application 6.2.5 for Android, the username and password are stored in the log during authentication, and may be available to attackers via logcat.