Re: Remotely exploitable firmware vulnerability in all Intel chipsets

2017-05-03 Thread Tom Buskey
On Tue, May 2, 2017 at 9:51 AM, Lloyd Kvam wrote: > lspci | egrep 'MEI|HECI' As the article on dreamwidth says, just having MEI doesn't mean you have AMT and the rest of the Intel ME working for someone to get in. Honestly, most of the stuff I've seen about ME reads like

Re: Remotely exploitable firmware vulnerability in all Intel chipsets

2017-05-02 Thread Lloyd Kvam
http://mjg59.dreamwidth.org/48429.html provides some Linux oriented info from Matthew Garrett lspci | egrep 'MEI|HECI' showed I have MEI On Tue, 2017-05-02 at 07:20 -0400, Ben Scott wrote: > This is potentially very bad for many people, as this is presumably exposed > outside the firewall on the

Remotely exploitable firmware vulnerability in all Intel chipsets

2017-05-02 Thread Ben Scott
This is potentially very bad for many people, as this is presumably exposed outside the firewall on the computer, and is OS-independent. That means any laptop that leaves a firewalled LAN is exposed to a remote root exploit. The Intel "Management Engine" (ME) runs along side the main processor.