<i>The short version is that every Intel platform with AMT, ISM, and SBT from Nehalem in 2008 to Kaby Lake in 2017 has a remotely exploitable security hole in the ME (Management Engine) not CPU firmware.</i><p>We knew this would happen. We knew that the Management Engine was a backdoor, and we knew it was only a matter of time before someone would figure out how to exploit it. This is exactly the reason why Libreboot exists (<a href="https://libreboot.org/faq.html#intel" rel="nofollow">https://libreboot.org/faq.html#intel</a>). And now, far from being the tinfoil hat distro that is often portrayed, it will become a bare necessity.
> For obvious reasons we couldn’t publish what we found<p>It's not obvious to me why anyone not under an NSL or NDA would sit on this vulnerability for 5 years and wait until it's actively being exploited in the wild before public disclosure.<p>It's extremely negligent to global security for SemiAccurate to not immediately publicly disclose the vulnerability 5 years ago after Intel refused to fix it. Of course this is ignoring the root of the problem, which is that the US government has deeply compromised Intel since the very first security management interfaces were added to Intel chips in the early 90s.<p>The real solution to the root issue is legislation that forces security disclose timelines of 90 days or less for government-found vulnerabilities, and prevents the stockpiling of vulnerability exploit kits.
Is there a better source for this than SemiAccurate? The article doesn't really have much beyond self-aggrandizement and "we can't tell you any details, but you're screwed". For something that could be anything from "Charlie Demerjian heard a rumor about a ME patch and wanted some pageviews" to the actual security apocalypse, I'd like credible sources.
>>every Intel platform with AMT, ISM, and SBT from Nehalem in 2008 to Kaby Lake in 2017 has a remotely exploitable security hole in the ME (Management Engine) not CPU firmware.<p>>>there is literally no Intel box made in the last 9+ years that isn’t at risk<p>>>SemiAccurate has been begging Intel to fix this issue for literally years<p>Am I the only one who is so cynical to think it must have been deliberate? Intel dragging their feet for YEARS -- what could justify such a delay? The paranoid side of me asks "Were they waiting to patch this hole, until they found a different one that could be utilized?"
Which begs the next quesion: Where is the NSA in all of this? It's the sort of thing that would be mighty handy to a group wishing to snoop on everyone and everything?<p>Last question: Why would anyone trust the encrypted management engine after this? (Why would anyone trust it before?)<p>>> What about embedded devices that are increasingly PC based? Digital signage perhaps? Industrial controls. HVAC. Security systems. Flight controls. Air traffic controls. Medical devices.<p>What, indeed? Is this the method used to interfere with Iran's nuclear program centrifuges?
As a sysadmin at a Windows shop, I don't know what to make of this. Has Intel commented on this, yet? Any OEM?<p>Joanna Rutkowska, who <i>is</i> a renowned security researcher, warned of something like this happening sooner or later[1], so I don't think I can afford to just ignore this.<p>But without something more specific to act on, there is nothing I <i>can</i> do, except wait firmware updates to be released by various vendors. <i>If</i> that happens.<p>And what if Intel does make a statement that essentially says, "This is all total BS"? I wouldn't know whether to believe them or not.<p>The only scenario where I could have any degree of certainty would be if Intel came out and said, "Yeah there's an exploitable security hole in ME, here's a patch to disable it".<p>[1] <a href="http://blog.invisiblethings.org/papers/2015/x86_harmful.pdf" rel="nofollow">http://blog.invisiblethings.org/papers/2015/x86_harmful.pdf</a>
Zero details and zero cross references, zero mentions on Google and zero mentions in any security list I'm on. Charlie blowing nonsensical steam yet again?
I think it is high time for companies who make hardware be financially fined for lapses like this. In this particular case, the manufacturer was warned and did nothing for years.<p>This is negligence especially considering these chips control critical devices that can cause damage or even loss of life if they are successfully exploited.<p>Can you imagine if car maker didn't fix a hardware defect they knew for years. Oh wait...
What is the motivation behind Management Engine?<p>From the perspective of an everyday user these things came out of nowhere to evolve into this para-computer running along side me that I cannot see and have no control of. It is on literally <i>ALL</i> hardware<p>Why is it that any attempts to disable it knock your whole computer out?<p>And this is the world of technology that we want? I'm so sick of technology companies appearing to work for their customers but secretly working against them.
<p><pre><code> Security is a cost center and most OEMs run on margins too thin
to bother with security patches even if they cared. Most simply don’t care.
</code></pre>
I think that sums up pretty well why downstream vendors are treating security casually. So the billion dollar question is, how do we fix this, as a tech community?
Great news that this finally came to light.<p>After learning about remote management capabilities I've always suspected it had holes. Large attack surface, any exploit would have a high value, and closed source.<p>Perhaps one day we'll be able to buy CPU's without this "feature".
I'm betting AMD and ARM are in the same boat.
"It is this last point that has been causing some political unrest in the US, and the rest of the Western world. As you undoubtedly know, China is very nearly the sole producer of all electronic goods. It would be very, very easy for the Chinese government to slip a hardware backdoor into the firmware of every iPad, smartphone, PC, and wireless router." 2012 <a href="https://www.extremetech.com/computing/133773-rakshasa-the-hardware-backdoor-that-china-could-embed-in-every-computer" rel="nofollow">https://www.extremetech.com/computing/133773-rakshasa-the-ha...</a><p>Made in China, designed in the USA. Everyone wants their own backdoor.
Patching is going to be a nightmare considering that many OEMs drop support for a motherboard after 3 years. There will be unpatched systems floating around for a very, very long time.
I've got a Lenovo T530 and a Lenovo T450s. I wonder if they've released a firmware update yet...?<p>I can't say I'm surprised, but I am surprised at the fact that finally, after all these years, someone finally got down to patching some vulnerabilities in this area.<p>props to whomever forced Intel's hand.
Can anyone add any details? The article is very very vague. Doesn't this work thru the Ethernet port in the chipset silicon?<p>So if you're running a desktop that has a physical Ethernet card in it, and the Intel Ethernet isn't connected, are you OK?<p>And if you're running on a laptop that uses Intel's Ethernet, (and most of them do?) then are you vulnerable?
Worrying about the ME and my dislike of secure boot is what has kept me from upgrading beyond the Core 2 Duo with BIOS. It's starting to feel slow now, but I still don't feel I can upgrade unless there is at least a way to disable the ME. So far, there don't seem to be any reliable methods of doing so.
Even without any newly discovered backdoor. The Intel ME was always a fu<i></i>ing security issue. A BACKDOOR. It is completely naive to think the NSA can't use the ME to get access to anything, but hey it needs another Snowden for people to listen again.
For those who cannot switch to Libreboot, <a href="https://github.com/corna/me_cleaner" rel="nofollow">https://github.com/corna/me_cleaner</a> may be a solution to this issue.
It'll be interesting to see how Intel deals with it.<p>Looking at the recent Atom failures (with vendors told in no uncertain terms to present publicly as generic "timing component" failure), will they even admit it's an ME thing?
Now this less-mainstream theory about the precarious state of our communication systems has confirmed to a greater degree, would anyone here know of similar risks that few seem to be aware of right now?<p>I'm not sure if this would be considered OT, but considering the nature and scope of these vulnerabilities I don't consider it reasonable to exclude the possibility of intent and malice.<p>For this reason I'd like to ask: what do you consider to be "the next, most likely to surface, conspiracy of this flavor"?<p>The flavor being: "the struggle for control of any and all data and computational resources".
I have a Sun workstation that seems to be no longer supported by Oracle (Sun Ultra 24 with a Q9300). I guess I'll just be vulnerable forever.<p>I don't really know what AMT does, but this has me thinking, if AMT is provisioned while a machine is used inside a company and then that machine shows up on eBay still provisioned, is it going to be phoning home and still be remotely manageable? How many of these machines have what are essentially persistent rootkits managed by large corporations that have had large fleets of laptops/desktops deployed that are then sold on?
I'm a total n00b to how this stuff works, but I can't seem to find any information for this sort of stuff online. I have an Intel CPU with a Gigabyte Motherboard and BIOS. If I'm running Linux without a GUI (headless) is this something that I have to worry about? If so, how do I turn it off? I don't see any options for the Intel AMT or ME in my BIOS settings.<p>EDIT: I have a Core i3-4130T. Looks like it doesn't have vPro so I'm hoping I'm safe?
My ignorance is showing, but what product lines are impacted?<p>Obviously things like Xeons and Core iXs, but what about things like Atom processors in tablets?
<i>Warning: Baseless, Idle Speculation</i><p>With the lead time on the silent patch before Shadow Brokers published all the Microsoft exploits, I wonder if Shadow Brokers will be publishing this one soon. No chance of an Intel ME patch going out without being noticed though!<p>A Shadow Brokers release would be a real mess.
Are remote management functions of portable consumer electronics (i.e.: remotely wiping your iPad) also supported by similar hardware chips from other vendors?
So they (SemiAccurate) knew about this for years, and STILL haven't bothered with disclosure to force Intel's hand earlier?<p>Thank you, SemiAccurate, for sitting on a vulnerability for years when you could've reported on it long ago and not had us left with this garbage of a security hole to deal with.
A back door is a back door is a back door.<p>Let's hope Intel and all the other chipmakers will learn this lesson (unless it's done on purpose, in which case they won't care about any lessons learned - they'll do it anyway).
I've always wondering why nobody seems to notice the fact that this site is literally called "Semi Accurate". I mean sure, everyone makes mistake and even the most credible news sources are not entirely accurate all the time. But what am I to think when your organization is literally named after being only half truthful?