Posted on 11/22/2017 1:44:20 PM PST by dayglored
Bugs can be exploited to extract info, potentially insert rootkits
Intel today admitted its Management Engine (ME), Server Platform Services (SPS), and Trusted Execution Engine (TXE) are vulnerable to multiple worrying security flaws, based on the findings of external security experts.
The firmware-level bugs allow logged-in administrators, and malicious or hijacked high-privilege processes, to run code beneath the operating system to spy on or meddle with the computer completely out of sight of other users and admins. The holes can also be exploited by network administrators, or people masquerading as admins, to remotely infect machines with spyware and invisible rootkits, potentially.
Meanwhile, logged-in users, or malicious or commandeered applications, can leverage the security weaknesses to extract confidential and protected information from the computer's memory, potentially giving miscreants sensitive data – such as passwords or cryptographic keys – to kick off other attacks. This is especially bad news on servers and other shared machines.
In short, a huge amount of Intel silicon is secretly running code that is buggy and exploitable by attackers and malware to fully and silently compromise computers. The processor chipsets affected by the flaws are as follows:
Intel's Management Engine, at the heart of today's disclosures, is a computer within your computer. It is Chipzilla's much maligned coprocessor at the center of its vPro suite of features, and it is present in various chip families. It has been assailed as a "backdoor" – a term Intel emphatically rejects – and it is a mechanism targeted by researchers at UK-based Positive Technologies, who are set to reveal in detail new ways to exploit the ME next month.
The Management Engine is a barely documented black box. it has its own CPU and its own operating system – recently, an x86 Quark core and MINIX – that has complete control over the machine, and it functions below and out of sight of the installed operating system and any hypervisors or antivirus tools present.
It is designed to allow network administrators to remotely or locally log into a server or workstation, and fix up any errors, reinstall the OS, take over the desktop, and so on, which is handy if the box is so messed up it can't even boot properly.
The ME runs closed-source remote-administration software to do this, and this code contains bugs – like all programs – except these bugs allow hackers to wield incredible power over a machine. The ME can be potentially abused to install rootkits and other forms of spyware that silently snoop on users, steal information, or tamper with files.
SPS is based on ME, and allows you to remotely configure Intel-powered servers over the network. TXE is Intel's hardware authenticity technology. Previously, the AMT suite of tools, again running on ME, could be bypassed with an empty credential string.
Today, Intel has gone public with more issues in its firmware. It revealed it "has identified several security vulnerabilities that could potentially place impacted platforms at risk" following an audit of its internal source code:
In response to issues identified by external researchers, Intel has performed an in-depth comprehensive security review of our Intel Management Engine (ME), Intel Server Platform Services (SPS), and Intel Trusted Execution Engine (TXE) with the objective of enhancing firmware resilience.
The flaws, according to Intel, could allow an attacker to impersonate the ME, SPS or TXE mechanisms, thereby invalidating local security features; "load and execute arbitrary code outside the visibility of the user and operating system"; and crash affected systems. The severity of the vulnerabilities is mitigated by the fact that most of them require local access, either as an administrator or less privileged user; the rest require you to access the management features as an authenticated sysadmin.
But as Google security researcher Matthew Garrett pointed out in the past hour or so, the aforementioned AMT flaw, if not patched, could allow remote exploitation.
In other words, if a server or other system with the AMT hole hasn't been updated to kill off that vulnerabilities, these newly disclosed holes will allow anyone on the network to potentially log in and execute malicious code within the powerful ME coprocessor.
"The ME compromise presumably gives you everything the AMT compromise gives you, plus more," said Garrett via Twitter. "If you compromise the ME kernel, you compromise everything on the ME. That includes AMT, but it also includes PTT."
He explained, "PTT is Intel's 'Run a TPM in software on the ME' feature. If you're using PTT and someone compromises your ME, the TPM is no longer trustworthy. That probably means your Bitlocker keys are compromised, but it also means all your remote attestation credentials are toast."
Garrett said if an exploit allows unsigned data to be installed and interpreted by the ME, an attacker could effectively trigger the reinfection of malware after every ME reboot. Were that to happen, the only way to fix things would be to reflash the hardware by hand. At that point, he said, it would probably be cheaper just to get new hardware.
Thanks, Intel. pic.twitter.com/w16IyKuCtu — The Register (@TheRegister) November 20, 2017
Intel said systems using ME Firmware versions 11.0, 11.5, 11.6, 11.7, 11.10, and 11.20, SPS Firmware version 4.0, and TXE version 3.0 are affected. The cited CVE-assigned bugs are as follows:
Chipzilla thanked Mark Ermolov and Maxim Goryachy at Positive for discovering and bringing to its attention the flaw CVE-2017-5705, which sparked the aforementioned review of its source code for vulnerabilities.
Intel advises Microsoft and Linux users to download and run the Intel-SA-00086 detection tool to determine whether their systems are vulnerable to the above bugs. If you are at risk, you must obtain and install firmware updates from your computer's manufacturer, if and when they become available. The new code was developed by Intel, but it needs to be cryptographically signed by individual hardware vendors in order for it to be accepted and installed by the engine.
Lenovo was quick off the mark with patches for its gear ready to download.
We'll give you a roundup of fixes as soon as we can. It's not thought Apple x86 machines are affected as they do not ship with Intel's ME, as far as we can tell.
Today's news will no doubt fuel demands for Intel to ship components free of its Management Engine – or provide a way to fully disable it – so people can use their PCs without worrying about security bugs on mysterious secluded coprocessors. ®
For those not aware of the Management Engine, it’s a separate, independent CPU, buried in the main CPU, that can run even with most other functions disabled or turned off. There are previous Windows Ping List threads on this topic.
Is this a flaw or is it one of those ‘features’ that the NSA blackmailed Intel into creating for them?
You can thank the guys that work in the “intelligence community”, who are the “cyberwarriors”, these days.
More like TSA rejects, if you ask me!
I spend more time than I care to think about updating my tech stuff. Or more precisely tracking down the updates.
Yes EMT ALWAYS has critical vulnerabilities... every couple months I get a new critical update email from our OEM.
Detection Error: This system may be vulnerable, please install the Intel(R) MEI/TXEI driver (available from your system manufacturer).
I don't have a system manufacturer, as I built this computer myself.
Maybe they can fix the deprecation routine that slows the PC down gradually over time until it simply fails to run anymore.
I never understood why a perfectly good computer running a limited number of application gradually slows to the point of unusability.
Thanks. Sent this to my SA and he came right back and said that he had already patched two of my systems. The rest are too old to be vulnerable.
Long-term slowdown is generally due to one or both of these:
Um Yeah
That’s what happens when you hire armies of H1-Bs to regurgitate CrapCode day and night
It has memory leaks, crashes all the time for no good reason, and has backdoors everywhere since nobody thought about it and the Configuration Mgmt guys didn’t know or care
On the disk clean-up, there are several items and I have no idea what is safe to delete and what should not be touched. For example, delivery optimization files.
I disabled mine in Device Manager a long time ago. Could find no one who knew why it was there or what it did. Just turn it off.
wonderful...
There are utilities within Windows that can reduce the number of unneeded files (e.g. Accessories -> System Tools -> Disk Cleanup), and third-party utilities that can do even more.
I won't offer specific advice on what files to delete on someone else's system. Ya never know what lurks.
Do a full backup before running any such programs. And run a "verify" pass on it. If you're like me, do two full backups, in case the first one has problems down the line.
You are more right than you know.
Intel Validation used to be one of the top notch groups within the company.
NOTHING got past this team without a really good reason.
Back 10 years ago, the Validation Team was forced (at threat of termination) to setup a validation group in Costa Rica.
Valued, experienced American workers were let go and the work was sent to Costa Rica.
About 3 years later, they started hearing reports of “Escapes” (Intel term for an ooops”
Validation Managers were thrown under the bus and blamed.
Very sad as great people were punished for something they were forced to implement.
http://www.thewindowsclub.com/can-i-delete-delivery-optimization-files-shown-by-disk-cleanup
If so, it does sound like you can delete them -IF- you have disabled Delivery Optimization (that link has details).
Do watch out for the ads on that page. Google has a number of other hits that might work better for you.
The latest Apple/Mac/iOS Pings can be found by searching Keyword "ApplePingList" on FreeRepublic's Search.
If you want on or off the Mac Ping List, Freepmail me
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.