[nSLUG] BIOS updating
D G Teed
donald.teed at gmail.com
Wed Jun 14 16:10:09 ADT 2017
I was puzzled by the whole thing when I read up on it a couple of weeks ago.
It is enabled on the BIOS of many systems, even if you don't have a vPro
However, it won't be listening unless the IP had been configured on the
to offer the management services. Once it is configured, that IP is alive
even when the system is powered off. Some newer systems have removed the
option from the BIOs to disable IME. It is like lights out or baseboard
built-in to the main ethernet interface on the mainboard.
Big risk for anyone who has configured it, but just something
to be aware of for the rest of us.
On Wed, Jun 14, 2017 at 11:00 AM, George N. White III <gnwiii at gmail.com>
> On 14 June 2017 at 08:16, Joel Maxuel <j.maxuel at gmail.com> wrote:
>> Thanks Dave. I missed the memo on the active IME exploit.
>> May not be much help to me anyway, based on the summary of changes for my
>> latest MoBo update:
>> I can check to see how bad it is, and what steps I can take tonight:
>> Thank you again.
> Some US Government employees were told to get rid of their Lenovo laptops
> last fall. Then in
> May Lenovo released Intel Management Engine Firmware 9.5 for my SSC issued
> laptop -- makes me wonder if US Gov't knew about IME exploits before they
> were made public,
> and if there are active exploits that still aren't public.
> Some articles suggest IME isn't an issue for linux users unless you use a
> high-end server
> farm that uses Intel's management tools, (possibly Google apps). That
> doesn't mean high-end
> malware won't leverage IME, but probably only after gaining full control
> of the system. For
> home linux systems there may not be much to be gained from IME based
> exploits, but it
> sounds like something TLA agencies would use, so will probably escape to
> sooner or later.
> George N. White III <aa056 at chebucto.ns.ca>
> Head of St. Margarets Bay, Nova Scotia
> nSLUG mailing list
> nSLUG at nslug.ns.ca
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nSLUG