[ingenium]

Hmm, I ensured the mei driver was loaded (lsmod confirms it), but I get: "Cannot open /dev/mei: No such file or directory"

dmesg shows: "[ 18.233688] mei_me 0000:00:16.0: Device doesn't have valid ME Interface [ 18.233700] mei_me 0000:00:16.1: Device doesn't have valid ME Interface"

So I'm guessing I'm not vulnerable. I suppose Supermicro replaced it with their own IPMI interface.

[pflanze]

Similarly, on an Intel NUC with i5-6260U:

    # git rev-parse HEAD
    9aa755885093fc8ca8c822797a30ed98ffe2e166
    # make
    gcc     mei-amt-check.c   -o mei-amt-check
    # modprobe mei-me
    # ./mei-amt-check -v
    Cannot open /dev/mei: No such file or directory
    # l /dev/*mei*
    /bin/ls: cannot access /dev/*mei*: No such file or directory
    # dmesg |grep -i mei
    #

A little confusing as the program is supposed to show "Intel AMT: DISABLED" 'If run on a system with no AMT'.

[pflanze]

OK, with commit a4d8fca4d18e1ae896b0305a53e152b568596bc1 (still after running modprobe mei_me) it is saying:

    Unable to find a Management Engine interface - run sudo modprobe mei_me and retry.
    If you receive the same error, this system does not have AMT

(Sounds good)

[HeadlessChild]

Fixed in this commit: https://github.com/mjg59/mei-amt-check/pull/4/commits/4f2fef...

[subway]

IPMI does not replace MEI. It sits off to the side. Odds are, MEI/AMT is off in your firmware.