Home | News | Download | Packages | Forum | Wiki | Github

Critical flaws in some Intel chips


#1

Just read a post on the Peppermint OS forum about this topic. See, https://thehackernews.com/2017/11/intel-chipset-flaws.html
To see if you are affected, https://downloadcenter.intel.com/download/27150
Just checked my laptop and I’m good :smiley:

[pin@awesomevoidmusl Downloads]$ sudo ./intel_sa00086.py 
INTEL-SA-00086 Detection Tool
Copyright(C) 2017, Intel Corporation, All rights reserved

Application Version: 1.0.0.135
Scan date: 2017-11-30 08:30:37 GMT

*** Host Computer Information ***
Name: awesomevoidmusl
Manufacturer: Hewlett-Packard
Model: HP ProBook 6470b
Processor Name: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
OS Version:    (4.13.15_1)

*** Intel(R) ME Information ***
Engine: Intel(R) Management Engine
Version: 8.1.0.1248
SVN: 0

*** Risk Assessment ***
Based on the analysis performed by this tool: This system is not vulnerable.

For more information refer to the INTEL-SA-00086 Detection Tool Guide or the Intel Security Advisory Intel-SA-00086 at the following link: https://www.intel.com/sa-00086-support

#2

Thank you @pin :+1:

Just checked my laptop and…

$ sudo ./intel_sa00086.py
INTEL-SA-00086 Detection Tool
Copyright(C) 2017, Intel Corporation, All rights reserved

Application Version: 1.0.0.135
Scan date: 2017-11-30 14:17:47 GMT

*** Host Computer Information ***
Name: pc2
Manufacturer: Hewlett-Packard
Model: HP Pavilion dv6 Notebook PC
Processor Name: Intel(R) Core(TM) i3 CPU       M 330  @ 2.13GHz
OS Version:    (4.13.15_1)

*** Risk Assessment ***
Detection Error: This system may be vulnerable, please install the Intel(R) MEI/TXEI driver (available from your system manufacturer).

For more information refer to the INTEL-SA-00086 Detection Tool Guide or the Intel Security Advisory Intel-SA-00086 at the following link: https://www.intel.com/sa-00086-support

I do not understand this:
"may be vulnerable..."

What does it mean ?
A system is vulnerable, or is not vulnerable.
Why using the conditional ??
This is misleading.
:unamused:


#3

Agree with you!
Have you decided what to do??:roll_eyes:


(oliver) #4

I’d guess the board has a signature they don’t understand so are erring on the side of caution


#5

uh… :thinking: I guess I should buy a new laptop, with an AMD CPU ? (just kidding…)

@oliver , did you check your computer with this tool ?


(oliver) #6

Nope - I have 3rd gen intel core

Below is the list of the processor chipsets which include the vulnerable firmware:
6th, 7th and 8th Generation Intel Core processors
Xeon E3-1200 v5 and v6 processors
Xeon Scalable processors
Xeon W processors
Atom C3000 processors
Apollo Lake Atom E3900 series
Apollo Lake Pentiums
Celeron N and J series processors


#7
INTEL-SA-00086 Detection Tool
Copyright(C) 2017, Intel Corporation, All rights reserved

Application Version: 1.0.0.135
Scan date: 2017-11-30 16:11:18 GMT

*** Host Computer Information ***
Name: schwifty
Manufacturer: Dell Inc.
Model: Inspiron 1545
Processor Name: Celeron(R) Dual-Core CPU       T3000  @ 1.80GHz
OS Version:    (4.14.2_1)

*** Risk Assessment ***
Detection Error: This system may be vulnerable, please install the Intel(R) MEI/TXEI driver (available from your system manufacturer).

For more information refer to the INTEL-SA-00086 Detection Tool Guide or the Intel Security Advisory Intel-SA-00086 at the following link: https://www.intel.com/sa-00086-support

Apparently I may be vulnerable. As @cr6 says, this is very frustrating and misleading. I wish Intel had simply not foisted ME/AMT upon its customers… however I run a Celeron T series so I doubt the risk factor.


(Benjamin) #8

This is fun, I don’t even get to know if I’m vunerable

INTEL-SA-00086 Detection Tool
Copyright(C) 2017, Intel Corporation, All rights reserved

Application Version: 1.0.0.135
Scan date: 2017-11-30 16:16:06 GMT

*** Host Computer Information ***
Name: benjamin-thinkpad-void
Manufacturer: LENOVO
Model: 6474WB8
Processor Name: Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz
OS Version:    (4.13.15_1)

Traceback (most recent call last):
  File "./intel_sa00086.py", line 133, in <module>
    sys.exit(main())
  File "./intel_sa00086.py", line 75, in main
    ver_str, code, family, svn = get_fw_state()
  File "/home/benjamin/Downloads/intel/SA00086_Linux/heci.py", line 91, in get_fw_state
    fw_ver = get_fw_ver()
  File "/home/benjamin/Downloads/intel/SA00086_Linux/heci.py", line 70, in get_fw_ver
    mei_fd = get_mkhi_fd()
  File "/home/benjamin/Downloads/intel/SA00086_Linux/heci.py", line 29, in get_mkhi_fd
    fixed_address_soft(dev_node, True)
  File "/home/benjamin/Downloads/intel/SA00086_Linux/mei/debugfs.py", line 88, in fixed_address_soft
    if get_fa_support(device):
  File "/home/benjamin/Downloads/intel/SA00086_Linux/mei/debugfs.py", line 121, in get_fa_support
    _, hbm = get_devstate(device)
  File "/home/benjamin/Downloads/intel/SA00086_Linux/mei/debugfs.py", line 98, in get_devstate
    mei_dir = check_for_debugfs(device)
  File "/home/benjamin/Downloads/intel/SA00086_Linux/mei/debugfs.py", line 69, in check_for_debugfs
    if not valid_path(mei_dir + '/meclients'):
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'


(Erin) #10

I got the same error running it on an AMD processor - yes I know but I had forgotten it was AMD not Intel!


#11

Don’t worry Intel Core Duos are really old, they don’t even have the coprocessor that this vulnerability is about. It’s crashing beacuse it can’t detect the coprocessor.
EDIT: I’m completly wrong there. I need to think before I write

This particular vulnerability won’t affect you as your CPU uses version 6 of ME which isn’t even in your CPU but in the PCH. It’s crashing beacuse it’s only designed to detect ‘modern’ versions of the ME.


#12

Mine is even older: it’s Westmere
:sweat_smile: phew!! seems like my cpu is not concerned then.


(Ben Hsu) #13

FYI, the Linux version of the detection script sucks.

I have a really old AMD machine that’s been running arch for a long time (my laptop is on void).

pobetiger@Gallahad $ ./intel_sa00086.py 
INTEL-SA-00086 Detection Tool
Copyright(C) 2017, Intel Corporation, All rights reserved

Application Version: 1.0.0.128
Scan date: 2017-11-25 01:14:30 GMT

*** Host Computer Information ***
Name: Gallahad
Manufacturer: System manufacturer
Model: System Product Name
Processor Name: AMD Phenom(tm) II X4 B50 Processor
OS Version: (4.13.12-1-ARCH)

*** Risk Assessment ***
Detection Error: This system may be vulnerable, please install the Intel(R) MEI/TXEI driver (available from your system manufacturer).

For more information refer to the SA-00086 Detection Tool Guide or the Intel security advisory Intel-SA-00086 at the following link:
https://security-center.intel.com/advisory.aspx...

Apparently, AMD machines also have IME! :wink:


#14

:roll_eyes: …the guy who wrote that program was probably tired at the time?


(Ben Hsu) #15

My guess: some interns or junior engineers did the work. That and poor code review process.

For one, they didn’t even check if the machine they’re running is Intel.

And think about how many more lines of code is in the IME…and none of it is open source!


#16

I’m vulnerable - well, thanks Intel! m(

INTEL-SA-00086 Detection Tool
Copyright(C) 2017, Intel Corporation, All rights reserved

Application Version: 1.0.0.135
Scan date: 2017-12-05 17:56:03 GMT

*** Host Computer Information ***
Name: dev
Manufacturer: GIGABYTE
Model: GB-BKi5(H)A-7200
Processor Name: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
OS Version:    (4.13.13_1)

*** Intel(R) ME Information ***
Engine: Intel(R) Management Engine
Version: 11.5.0.1058
SVN: 1

*** Risk Assessment ***
Based on the analysis performed by this tool: This system is vulnerable.
Explanation:
The detected version of the Intel(R) Management Engine firmware is considered vulnerable for INTEL-SA-00086.
Contact your system manufacturer for support and remediation of this system.


For more information refer to the INTEL-SA-00086 Detection Tool Guide or the Intel Security Advisory Intel-SA-00086 at the following link: https://www.intel.com/sa-00086-support

#17

yeah nice work Intel. :clap: :face_with_thermometer:


#18

Pffff I’ve just boght a new shiny laptop and I’m affected. Looking on how to deactivate this feature, I also found this:

Maybe fake but WTF is this society!?


#19

In such cases, will Intel compensate its customers? :unamused: (we can always dream…)

Where did you find this @r4nd0m6uy ? That’s incredible, and frightening! :grimacing:


#20

:scream: nasty but, unfortunately not surprising :sob:


#21

It’s from a chan so it may not all be true. What definitely is true is ME’s capabilities:
https://schd.ws/hosted_files/osseu17/84/Replace%20UEFI%20with%20Linux.pdf#page=6

Also it’s not the easiest to remove, I think at the moment only https://github.com/corna/me_cleaner can remove it, and that requires flashing your BIOS chip.

Although it won’t be long before we will be able to run Doom on the ME. /s