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

09:35 AM
Larry Loeb
Larry Loeb
Larry Loeb

AMD Chips Have Their Own Massive Hardware Security Flaws

CTS-Labs issued a report this week that detailed 13 different vulnerabilities in AMD's Ryzen and EPYC processors that are as dangerous as the Spectre and Meltdown flaws that Intel has been trying to fix.

After smiling smugly at Intel's Spectre and Meltdown chip problems and claiming its CPU architecture prevented these vulnerabilities from happening on its hardware, it's AMD's turn to face the music -- big time.

CTS-Labs, a security company based in Israel, announced on March 13 that its researchers had found 13 critical security vulnerabilities affecting data that is stored on AMD's Ryzen and EPYC processors. There is no current mediation for them, although CTS notes it is not releasing proof-of-concept exploitation code.

In addition, CTS has seemingly only given AMD 24 hours notice before publishing its findings.

The reported problems break down into four categories, and allow an attacker to target the secure segment of a processor.

The Masterkey variant installs malware on the BIOS, which is the segment that controls startup processes. This is supposed to ensure a tamper-proof startup. However, CTS finds that the injection is due to multiple vulnerabilities in the AMD Secure Processor firmware, which allows attackers to infiltrate the Secure Processor.

This will allow tampering with AMD's firmware-based security features such as Secure Encrypted Virtualization (SEV) and Firmware Trusted Platform Module (fTPM). In turn, it facilitates stealthy and persistent malware, which would be resilient against security solutions currently on the market.

This exploit is found by CTS to affect the EPYC server chips, as well as the Ryzen Workstation, Mobile and Pro processors.

Ryzenfall affects Ryzen Workstation, Mobile and Pro chips, and allows a complete takeover of the AMD Secure Processor. The SP privileges could be leveraged to read and write protected memory areas, such as SMRAM and the Windows Credential Guard isolated memory.

This could allow attackers using the vulnerability to bypass Windows Credential Guard and obtain network credentials that allow the attack to spread over a network.

Fallout affects the EPYC server -- the processor Microsoft chose for its Azure cloud servers -- and enables attackers to read from and write to protected memory areas. This could include SMRAM and Windows Credential Guard isolated memory (VTL-1). Again, this could allow network credentials to be obtained.

Additionally, leveraging the vulnerabilities could bypass BIOS flashing protections that are implemented in SMM.

The last category, Chimera, consists of two manufacturer backdoors in the Ryzen Workstation and Pro. One is in firmware and the other in ASIC hardware. These allow for injection of malicious code. Since these chips link the CPU to USB, SATA, and PCI-E devices, these exploits could affect network, WiFi and Bluetooth traffic. The Direct Memory Access (DMA) engine could also be attacked to affect the operating system.

The fundamentals of network security are being redefined -- don't get left in the dark by a DDoS attack! Join us in Austin from May 14-16 at the fifth annual Big Communications Event. There's still time to register and communications service providers get in free!

CTS reported that the experts that it has consulted with noted that the firmware vulnerabilities such as Masterkey, Ryzenfall and Fallout would take several months to fix. Not only that, hardware vulnerabilities such as Chimera cannot be fixed and require a workaround.

Producing a workaround may be difficult and cause undesired side-effects, according to CTS.

CTS has shared the vulnerability information with AMD, Microsoft, and a small number of companies that could produce patches and mitigations. As of this writing, AMD has issued no definitive statement, other than to note that the company is investigating.

Without testable POC code, however, it is impossible to verify that all of CTS's statements are accurate. Therefore, the warnings may be taken with some reservation even though it's possible that they are valid.

In any case, it seems AMD has some massive work that needs to be undertaken to rectify these claims.

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
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/27/2020
Modern Day Insider Threat: Network Bugs That Are Stealing Your Data
David Pearson, Principal Threat Researcher,  10/21/2020
Are You One COVID-19 Test Away From a Cybersecurity Disaster?
Alan Brill, Senior Managing Director, Cyber Risk Practice, Kroll,  10/21/2020
Register for Dark Reading Newsletters
White Papers
Current Issue
Special Report: Computing's New Normal
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-10-27
All versions of package trim are vulnerable to Regular Expression Denial of Service (ReDoS) [DNP] via trim().
PUBLISHED: 2020-10-27
Multiple cross-site scripting (XSS) vulnerabilities in konzept-ix publiXone before 2020.015 allow remote attackers to inject arbitrary JavaScript or HTML via appletError.jsp, job_jacket_detail.jsp, ixedit/editor_component.jsp, or the login form.
PUBLISHED: 2020-10-27
A RemoteFunctions endpoint with missing access control in konzept-ix publiXone before 2020.015 allows attackers to disclose sensitive user information, send arbitrary e-mails, escalate the privileges of arbitrary user accounts, and have unspecified other impact.
PUBLISHED: 2020-10-27
Pulse Secure Desktop Client 9.0Rx before 9.0R5 and 9.1Rx before 9.1R4 on Windows reveals users' passwords if Save Settings is enabled.
PUBLISHED: 2020-10-27
An XML external entity (XXE) vulnerability in Pulse Connect Secure (PCS) before 9.1R9 and Pulse Policy Secure (PPS) before 9.1R9 allows remote authenticated admins to conduct server-side request forgery (SSRF) attacks via a crafted DTD in an XML request.