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.

ABTV

End of Bibblio RCM includes -->
11/29/2017
01:05 PM
Larry Loeb
Larry Loeb
Larry Loeb

Intel Management Engine Has a Big Problem

Intel's Management Engine has a vulnerability that could allow an attacker to own your entire system. And they aren't planning to fix it.

Intel has finally 'fessed up that their Management Engine (ME) —- which is the computer that runs on top of your computer that uses Intel chips -— has a few vulnerabilities in it.

Nothing to be worried about, but they did find that attackers could gain unauthorized access to systems using the ME as well as the third-party secrets protected by the Management Engine (ME), Server Platform Service (SPS), or the Trusted Execution Engine (TXE). After that they could just light your code on fire using torches held aloft by sticks, just like in the movies.

Intel says that attackers can impersonate the ME/SPS/TXE, "thereby impacting local security feature attestation validity." Like running it into the ground and smashing it kind of impacting.

Not only that, attackers could "load and execute arbitrary code outside the visibility of the user and operating system and cause a system crash or system instability."

Wee doggies, that's some nasty impacting going on there. And it gets worse.

There's something called Active Management Technology (AMT) that runs on top of ME, which is already on top of what you think is your computer system. Some of the vulnerabilities target AMT. They can enable remote administration, remote display viewing/scraping, injecting human interface device (HID) events, and disabling the secure boot configuration. Some of what it can attack may not require the main operating system to be running or even the main system to be powered on. It just has to be plugged in to be exposed.

While there are no known, active or malicious exploits for these vulnerabilities at this time don't be lulled into a sense of ease. Yes, local system access is required to exploit most of them. But Intel admits that if the "management" Ethernet port is available, attackers may be able to combine older vulnerabilities along with the new weaknesses to access the ME/AMT components without having to be directly on the attacked systems.

There's a detection tool that can be run to see if the machine is at risk. (Apple's computers aren't at risk, btw.)

Intel's strategy for mitigation here is to let the manufacturers come up with patches for their own machines. And you, of course, have to find a way to manage updating and patching every doggone machine on your network. All of them.

The only other option is to buy all new machines. Which you hope have been factory fixed before you buy them.

This whole affair is majorly disruptive. Both time and money that could have been gainfully used elsewhere will end up being funneled to deal with it. Worse, there is a very low awareness of the scope of the problem among IT people.

But you know about it now. Start running.

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
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Improving Enterprise Cybersecurity With XDR
Enterprises are looking at eXtended Detection and Response technologies to improve their abilities to detect, and respond to, threats. While endpoint detection and response is not new to enterprise security, organizations have to improve network visibility, expand data collection and expand threat hunting capabilites if they want their XDR deployments to succeed. This issue of Tech Insights also includes: a market overview for XDR from Omdia, questions to ask before deploying XDR, and an XDR primer.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-2304
PUBLISHED: 2022-07-05
Stack-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.
CVE-2022-26365
PUBLISHED: 2022-07-05
Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33...
CVE-2022-30290
PUBLISHED: 2022-07-05
In OpenCTI through 5.2.4, a broken access control vulnerability has been identified in the profile endpoint. An attacker can abuse the identified vulnerability in order to arbitrarily change their registered e-mail address as well as their API key, even though such action is not possible through the...
CVE-2022-33740
PUBLISHED: 2022-07-05
Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33...
CVE-2022-33741
PUBLISHED: 2022-07-05
Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33...