Intel Management Engine

Several weaknesses have been found in the ME. On May 1, 2017, Intel confirmed a Remote Elevation of Privilege bug (SA-00075) in its Management Technology. [15] Every Intel platform with provisioned Intel Standard Manageability, Active Management Technology, or Small Business Technology, from Nehalem in 2008 to Kaby Lake in 2017 has a remotely exploitable security hole in the ME. [16] [17] Several ways to disable the ME without authorization that could allow ME's functions to be sabotaged have been found. [18] [19] [20] Additional major security flaws in the ME affecting a very large number of computers incorporating ME, Trusted Execution Engine (TXE), and Server Platform Services (SPS) firmware, from Skylake in 2015 to Coffee Lake in 2017, were confirmed by Intel on 20 November 2017 (SA-00086). [21] Unlike SA-00075, this bug is even present if AMT is absent, not provisioned or if the ME was "disabled" by any of the known unofficial methods. [22] In July 2018 another set of vulnerabilitites were disclosed (SA-00112). [23] In September 2018, yet another vulnerability was published (SA-00125). [24]

The Electronic Frontier Foundation (EFF) and security expert Damien Zammit accuse the ME of being a backdoor and a privacy concern. [13] [4] Zammit states that the ME has full access to memory (without the parent CPU having any knowledge); has full access to the TCP/IP stack and can send and receive network packets independent of the operating system, thus bypassing its firewall. [12] Intel asserts that it "does not put back doors in its products" and that its products do not "give Intel control or access to computing systems without the explicit permission of the end user." [12] [14]

The Management Engine is often confused with Intel AMT . AMT runs on the ME, but is only available on processors with vPro . AMT enables owners remote administration of their computer, [12] like turning it on or off and reinstalling the operating system. However, the ME itself is built into all Intel chipsets since 2008, not only those with AMT. While AMT can be unprovisioned by the owner, there is no official, documented way to disable the ME.

The Intel Management Engine ( ME ), also known as the Manageability Engine, [1] [2] is an autonomous subsystem that has been incorporated in virtually all of Intel's processor chipsets since 2008. [3] [4] [1] The subsystem primarily consists of proprietary firmware running on a separate microprocessor that performs tasks during boot-up, while the computer is running, and while it is asleep. [5] As long as the chipset or SoC is connected to current (via battery or power supply), it continues to run even when the system is turned off. [6] Intel claims the ME is required to provide full performance. [7] Its exact workings [8] are largely undocumented [9] and its code is obfuscated using confidential huffman tables stored directly in hardware, so the firmware does not contain the information necessary to decode its contents. [10] Intel's main competitor AMD has incorporated the equivalent AMD Secure Technology (formally called Platform Security Processor) in virtually all of its post-2013 CPUs. [11]

Privilege rings for the x86 . The ME is colloquially categorized as ring -3, below System Management Mode (ring -2) and the hypervisor (ring -1), all running at a higher privilege level than the kernel (ring 0)

By Intel's current terminology as of 2017, ME is one of several firmware sets for the Converged Security and Manageability Engine (CSME). Prior to AMT version 11, CSME was called Intel Management Engine BIOS Extension (Intel MEBx). [1]

The ME has its own MAC and IP address for the out-of-band interface, with direct access to the Ethernet controller; one portion of the Ethernet traffic is diverted to the ME even before reaching the host's operating system, for what support exists in various Ethernet controllers, exported and made configurable via Management Component Transport Protocol (MCTP). [27] [28] The ME also communicates with the host via PCI interface. [26] Under Linux, communication between the host and the ME is done via /dev/mei . [29]

Disabling the ME

Edit

It is normally not possible for the user to disable the ME. Potentially risky, undocumented methods to do so were discovered, however.[21] These methods are not supported by Intel. The ME's security architecture is supposed to prevent disabling, and thus its possibility is considered a security vulnerability. For example, a virus could abuse it to make the computer lose some of the functionality that the typical end-user expects, such as the ability to play media with DRM. Yet, critics consider the weaknesses not as bugs, but as features.

Strictly speaking, none of the known methods disables the ME completely, since it is required for booting the main CPU. All known methods merely make the ME go into abnormal states soon after boot, in which it seems not to have any working functionality. The ME is still physically connected to the current and its microprocessor is continuing to execute code.

Undocumented methods

Edit

Firmware neutering

Edit

In 2016, the me_cleaner project found that the ME's integrity verification is broken. The ME is supposed to detect that it has been tampered with, and, if this is the case, shut down the PC forcibly after 30 minutes.[44] This prevents a compromised system from running undetected, yet allows the owner to fix the issue by flashing a valid version of the ME firmware during the grace period. As the project found out, by making unauthorized changes to the ME firmware, it was possible to force it into an abnormal error state that prevented triggering the shutdown even if large parts of the firmware had been overwritten and thus made inoperable.

"High Assurance Platform" mode

Edit

In August 2017, Russian company Positive Technologies (Dmitry Sklyarov) published a method to disable the ME via an undocumented built-in mode. As Intel has confirmed[45] the ME contains a switch to enable government authorities such as the NSA to make the ME go into High-Assurance Platform (HAP) mode after boot. This mode disables all of ME's functions[citation needed]. It is authorized for use by government authorities only and is supposed to be available only in machines produced for them. Yet it turned out that most machines sold on the retail market can be tricked into activating the switch.[46][47]. Manipulation of the HAP bit was quickly incorporated into the me_cleaner project[48].

Commercial ME disablement

Edit

In late 2017, several laptop vendors announced their intentions to ship laptops with the Intel ME disabled:

  • Purism previously petitioned Intel to sell processors without the ME, or release its source code, calling it "a threat to users' digital rights"[49]. In March 2017, Purism announced[50] that it had neutralized the ME by erasing the majority of the ME code from the flash memory. It further announced in October 2017[51] that new batches of their Debian-based Librem line of laptops will ship with the ME neutralized (via erasing the majority of ME code from the flash, as previously announced), and additionally disabling most ME operation via the HAP bit. Updates for existing Librem laptops were also announced.
  • System 76 announced in November 2017[52] their plan to disable the ME on their new and recent Ubuntu-based machines via the HAP bit.
  • Dell, in December 2017,[53] began showing certain laptops on its website that offered the "Systems Management" option "Intel vPro - ME Inoperable, Custom Order" for an additional fee. Dell has not announced or publicly explained the methods used. In response to press requests, Dell stated that those systems had been offered for quite a while, but not for the general public, and had found their way to the website only inadvertently.[54] The laptops are available only by custom order and only to military, government and intelligence agencies.[55] They are specifically designed for covert operations, such as providing a very robust case and a "stealth" operating mode kill switch that disables display, LED lights, speaker, fan and any wireless technology[56].

Effectiveness against vulnerabilities

Edit

None of the two methods to disable the ME discovered so far turned out to be an effective countermeasure against the SA-00086 vulnerability.[57] This is because the vulnerability is in an early-loaded ME module that is essential to boot the main CPU.[58]

Ring −3 rootkitEdit

A ring −3 rootkit was demonstrated by Invisible Things Lab for the Q35 chipset; it does not work for the later Q45 chipset as Intel implemented additional protections.[59] The exploit worked by remapping the normally protected memory region (top 16 MB of RAM) reserved for the ME. The ME rootkit could be installed regardless of whether the AMT is present or enabled on the system, as the chipset always contains the ARC ME coprocessor. (The "−3" designation was chosen because the ME coprocessor works even when the system is in the S3 state, thus it was considered a layer below the System Management Mode rootkits.[30]) For the vulnerable Q35 chipset, a keystroke logger ME-based rootkit was demonstrated by Patrick Stewin.[60][61]

Zero-touch provisioning

Edit

Another security evaluation by Vassilios Ververis showed serious weaknesses in the GM45 chipset implementation. In particular, it criticized AMT for transmitting unencrypted passwords in the SMB provisioning mode when the IDE redirection and Serial over LAN features are used. It also found that the "zero touch" provisioning mode (ZTC) is still enabled even when the AMT appears to be disabled in BIOS. For about 60 euros, Ververis purchased from Go Daddy a certificate that is accepted by the ME firmware and allows remote "zero touch" provisioning of (possibly unsuspecting) machines, which broadcast their HELLO packets to would-be configuration servers.[62]

SA-00075 (aka Silent Bob is Silent)

Edit

In May 2017, Intel confirmed that many computers with AMT have had an unpatched critical privilege escalation vulnerability (CVE-2017-5689).[17][63][15][64][65] The vulnerability, which was nicknamed "Silent Bob is Silent" by the researchers who had reported it to Intel,[66] affects numerous laptops, desktops and servers sold by Dell, Fujitsu, Hewlett-Packard (later Hewlett Packard Enterprise and HP Inc.), Intel, Lenovo, and possibly others.[66][67][68][69][70][71][72] Those researchers claimed that the bug affects systems made in 2010 or later.[73] Other reports claimed the bug also affects systems made as long ago as 2008.[74][17] The vulnerability was described as giving remote attackers:

"full control of affected machines, including the ability to read and modify everything. It can be used to install persistent malware (possibly in firmware), and read and modify any data."

Tatu Ylönen, ssh.com[66]

PLATINUM

Edit

In June 2017, the PLATINUM cybercrime group became notable for exploiting the serial over LAN (SOL) capabilities of AMT to perform data exfiltration of stolen documents.[75][76][77][78][79][80][81][82]

Some months after the previous bugs, and subsequent warnings from the EFF,[4] security firm Positive Technologies claimed to have developed a working exploit.[83] On 20 November, 2017 Intel confirmed that a number of serious flaws had been found in the Management Engine (mainstream), Trusted Execution Engine (tablet/mobile), and Server Platform Services (high end server) firmware, and released a "critical firmware update".[84][85] Essentially every Intel-based computer for the last several years, including most desktops and servers, were found to be vulnerable to having their security compromised, although all the potential routes of exploitation were not entirely known.[85] It is not possible to patch the problems from the operating system, and a firmware (UEFI, BIOS) update to the motherboard is required, which was anticipated to take quite some time for the many individual manufacturers to accomplish, if it ever would be for many systems.[21]

[84]

Affected systems

Edit

  • Intel Atom – C3000 family
  • Intel Atom – Apollo Lake E3900 series
  • Intel Celeron – N and J series
  • Intel Core (i3, i5, i7, i9) – 1st, 2nd, 3rd, 4th, 5th, 6th, 7th, and 8th generation
  • Intel Pentium – Apollo Lake
  • Intel Xeon – E3-1200 v5 and v6 product family
  • Intel Xeon – Scalable family
  • Intel Xeon – W family

Mitigation

Edit

None of the known unofficial methods to disable the ME prevent exploitation of the vulnerability. A firmware update by the vendor is required. However, those who discovered the vulnerability note that firmware updates are not fully effective either, as an attacker with access to the ME firmware region can simply flash an old, vulnerable version and then exploit the bug.[86]

In July 2018 Intel announced that 3 vulnerabilities (CVE-2018-3628, CVE-2018-3629 and CVE-2018-3632) had been discovered and that a patch for the CSME firmware would be required. Intel indicated there would be no patch for 3rd generation Core processors or earlier despite chips or their chipsets as far back as Intel Core 2 Duo vPro and Intel Centrino 2 vPro being affected.[23]

Similar Articles:

Intel Patched A Vulnerability Leaking Intel ME Encryption Keys

Intel Patched A Vulnerability Leaking Intel ME Encryption Keys

Intel ME's Undocumented Manufacturing Mode Suggests CPU Hacking Risks

Intel ME's Undocumented Manufacturing Mode Suggests CPU Hacking Risks

Foreshadow/L1TF Intel Processor Vulnerabilities: What You Need to Know

Foreshadow/L1TF Intel Processor Vulnerabilities: What You Need to Know

The Intel Management Engine: an attack on computer users' freedom — Free Software Foundation — working together for free software

The Intel Management Engine: an attack on computer users' freedom — Free Software Foundation — working together for free software