Author Topic: A Security Issue in Intel’s Active Management Technology (AMT)  (Read 210 times)

Offline javajolt

  • Administrator
  • Hero Member
  • *****
  • Posts: 35126
  • Gender: Male
  • I Do Windows
    • windows10newsinfo.com
Misleading behavior within Intel's technology allows a local attacker to compromise and take control of work laptops.

Imagine someone having the capability to remotely access and operate your laptop at their whim, without you being able to do anything about it. Pretty scary thought, right? Luckily this couldn’t really happen – magic hacker tricks capable of bypassing strong passwords, firewalls and anti-malware software only exist in the movies.

It’s just that sometimes reality kicks fiction right in the teeth. In July 2017 Harry Sintonen, one of F-Secure’s Senior Security Consultants, discovered unsafe and misleading default behavior within Intel’s Active Management Technology (AMT). AMT is Intel’s proprietary solution for remote access monitoring and maintenance of corporate-grade personal computers, created to allow IT departments or managed service providers to better control their device fleets.

AMT is no stranger to security weaknesses, with many other researchers finding multiple flaws within the system, but Sintonen’s discovery surprised even him. The security issue seems like something lifted straight from IT security officers’ worst nightmares.

“The attack is almost deceptively simple to enact, but it has incredible destructive potential. In practice, it can give a local attacker complete control over an individual’s work laptop, despite even the most extensive security measures,” Sintonen says.

So how can this be exploited in practice?

The issue allows a local intruder to backdoor almost any corporate laptop in a matter of seconds, even if the BIOS password, TPM Pin, BitLocker and login credentials are in place. No, we’re not making this stuff up.

The setup is simple: an attacker starts by rebooting the target’s machine, after which they enter the boot menu. In a normal situation, an intruder would be stopped here; as they won’t know the BIOS password, they can’t really do anything harmful to the computer.

In this case, however, the attacker has a workaround: AMT. By selecting Intel’s Management Engine BIOS Extension (MEBx), they can log in using the default password “admin,” as this hasn’t most likely been changed by the user. By changing the default password, enabling remote access and setting AMT’s user opt-in to “None”, a quick-fingered cybercriminal has effectively compromised the machine. Now the attacker can gain access to the system remotely, as long as they’re able to insert themselves into the same network segment with the victim (enabling wireless access requires a few extra steps).

Although the successful exploitation of the security issue requires physical proximity, this might not be as difficult for skilled attackers to organize as you might think. Sintonen lays out one probable scenario, using techniques common to cyber criminals and red teamers alike.

“Attackers have identified and located a target they wish to exploit. They approach the target in a public place – an airport, a café or a hotel lobby – and engage in an ‘evil maid’ scenario. Essentially, one attacker distracts the mark, while the other briefly gains access to his or her laptop. The attack doesn’t require a lot of time – the whole operation can take well under a minute to complete,” Sintonen says.

Combating the issue

Although solid operations security is the first step (don’t ever leave your laptop unwatched in an insecure location!), there are some basic safeguards all IT departments should implement.

The system provisioning process needs to be updated to include setting a strong password for AMT or disabling it completely if possible. IT should also go through all currently deployed machines, and organize the same procedure for them. Intel’s own recommendations for using AMT in a secure manner follow similar logic.

Now, this might be more difficult than it sounds. IT departments might find it increasingly tricky to remediate the issue on a large scale, as the required changes may be difficult to effect remotely (ironically enough). In most cases, a mass reconfiguration effort of affected devices is the only way to deal with AMT issues – not fun for a large, global organization. Our recommendation is to query the number of affected assets remotely 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.

Most importantly: if the AMT password has been set to an unknown value on a user’s laptop, consider the device suspect and initiate an incident response. The first rule of cybersecurity? Never take unnecessary risks.

For more information on the issue, download our FAQ here!

View full advisory

source
« Last Edit: January 14, 2018, 01:24:36 AM by javajolt »