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 Security //

Windows

1/16/2018
09:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

After Spectre & Meltdown, Intel Faces an 'Evil Maid' Problem

In a rough start to 2018, Intel is dealing with the Spectre and Meltdown vulnerabilities in its CPUs, and now the chip maker is confronting reports of a flaw that leaves chips open to an 'Evil Maid' attack.

It's only a few weeks old, but 2018 has not been a good year for Intel.

Since the start of the year, most tech headlines have focused on the major problems and security flaws that have been found in Intel's CPU designs -- now referred to as Spectre and Meltdown -- as well as reports of security holes in the Advanced Management Technology (AMT) program that runs the bits through the processors. (See Security Warning: Intel Inside.)

Now, add one more problem to the list.

Harry Sintonen, a senior researcher at F-Secure Corp. , announced last week that he had found a way for someone who gains physical access for under 60 seconds to a computer that uses an Intel Corp. (Nasdaq: INTC) CPU to be able to poison it so that it could be hijacked remotely if the attacker is on the same network.

This kind of attack is called an "Evil Maid" -- a machine left open for a moment public space could be compromised by a threat actor. This type of attack takes its name from the scenario of an evil maid who carries out the attack on a computer that is left in a hotel room.

The attack is simple and deadly.

Booting up the device and pressing CTRL-P during the process starts it. This causes the attacker to log in to the Intel Management Engine BIOS Extension (MEBx), which has credentials that are unrelated to any other system passwords, TPM pin or Bitlocker settings. The usual MEBx default password "admin" will gain access to the AMT on most machines.

The attacker could then reset the default password, enabling remote access and setting AMT's user opt-in to "None."

Boom -- a compromised machine. All the other passwords and logins in effect can be bypassed remotely if the attacker is on the same network segment. If the attackers get AMT to log into their own server, they don't even have to be on the same network segment to control the machine.

So, what can you do about this? One answer is to just throw out AMT but an IT department may not be able to do this remotely.

F-Secure seems to understand that, and offers the following advice:

Our recommendation is to query the amount of affected assets remotely [to find the machines with a non-"admin" MEBx password], and try to narrow the list down to a more manageable number. Organizations with Microsoft environments and domain connected devices can also take advantage of the System Center Configuration Manager to provision AMT.

There is no CVE number for this problem, nor is there any announcement scheduled from Intel. Organizations are on their own, here.

While Intel has written guides to dealing with AMT, the company may not have considered how the real world or evil maids can affect security. Leaving a laptop unsecured in a public place is never a good idea, in any case.

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
How Enterprises are Attacking the Cybersecurity Problem
Concerns over supply chain vulnerabilities and attack visibility drove some significant changes in enterprise cybersecurity strategies over the past year. Dark Reading's 2021 Strategic Security Survey showed that many organizations are staying the course regarding the use of a mix of attack prevention and threat detection technologies and practices for dealing with cyber threats.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-41163
PUBLISHED: 2021-10-20
Discourse is an open source platform for community discussion. In affected versions maliciously crafted requests could lead to remote code execution. This resulted from a lack of validation in subscribe_url values. This issue is patched in the latest stable, beta and tests-passed versions of Discour...
CVE-2021-42299
PUBLISHED: 2021-10-20
Microsoft Surface Pro 3 Security Feature Bypass Vulnerability
CVE-2021-42771
PUBLISHED: 2021-10-20
Babel.Locale in Babel before 2.9.1 allows attackers to load arbitrary locale .dat files (containing serialized Python objects) via directory traversal, leading to code execution.
CVE-2021-42764
PUBLISHED: 2021-10-20
The Proof-of-Stake (PoS) Ethereum consensus protocol through 2021-10-19 allows an adversary to cause a denial of service (delayed consensus decisions), and also increase the profits of individual validators, via short-range reorganizations of the underlying consensus chain.
CVE-2021-42765
PUBLISHED: 2021-10-20
The Proof-of-Stake (PoS) Ethereum consensus protocol through 2021-10-19 allows an adversary to leverage network delay to cause a denial of service (indefinite stalling of consensus decisions).