News for hackers. Stuff that matters.
Re:Intel patches new ME vulnerabilities by nh2 on Sunday July 22, 2018 @09:12AM (#17586560)
Intel advisory: https://www.intel.com/content/www/us/en/security-center/advi...

CVE-2018-3628 - "Buffer overflow in HTTP handler"

Affected processor list (simplified reordered by me to reflect relevance and improve readability):

• Core i3/i5/i7, generation 1-8 (that is, all of them)

• Xeon E3-1200 v5/v6

• Xeon Scalable

• Xeon W

• Core 2 Duo vPro, Centrino 2 vPro

Re:Intel patches new ME vulnerabilities by Macha on Sunday July 22, 2018 @09:27AM (#17586616)
Also worth noting that they're not patching it for 1st, 2nd or 3rd generation Core CPUs. I'm sure there's plenty of Sandy Bridge/Ivy Bridge CPUs in the wild, and it's not like you have an option to discontinue use of the Intel ME :(
Re:Intel patches new ME vulnerabilities by Kliment on Sunday July 22, 2018 @11:48AM (#17587290)
There's always me_cleaner. It's a bit of a pain and requires hardware access to run but better than being exposed to an unpatchable vuln. I encourage every hackspace to set up an ME removal station (I'm building one for EMF Camp this year, and will document it so others can easily replicate)
Re:Intel patches new ME vulnerabilities by confounded on Sunday July 22, 2018 @07:49PM (#17589525)
Please do! I would love to do this, but am far too much of a sissy to mess with SPI flash. I've subscribed to your RSS feed. Do drop any guides/artifacts in the Noisebridge IRC when you have them :)
Re:Intel patches new ME vulnerabilities by Kliment on Monday July 23, 2018 @12:49AM (#17590653)
Mitch will be at EMF, probably in a tent adjacent to mine. So I'll just ask him to bring the knowledge back to noisebridge.
Re:Intel patches new ME vulnerabilities by rectang on Sunday July 22, 2018 @09:55AM (#17586747)
Planned obsolescence of otherwise viable product implemented via a certain-to-be-exploited architecture (the ME) followed by strategic withholding of patches?
Re:Intel patches new ME vulnerabilities by 21 on Sunday July 22, 2018 @11:34AM (#17587232)
That's quite a conspiracy theory you got there. Things like these make people look at AMD again.
Re:Intel patches new ME vulnerabilities by rectang on Sunday July 22, 2018 @11:45AM (#17587276)
It doesn't have to have been a full-blown plan from years ago in order to be a viable strategy. Intel can choose planned obsolescence going forward today for selected products by not developing or releasing security patches.

The extent to which this particular strategic business option was discussed during the design phase of the ME is hard to know from the outside. Surely someone within Intel pointed out that the ME was inherently insecure, but as for all the consequences, who knows?

Re:Intel patches new ME vulnerabilities by 21 on Sunday July 22, 2018 @11:58AM (#17587336)
There are many ways to to planned obsolescence. I'm sure there is a way to just manufacture the chips such that they degrade in a few years.

Planned obsolescence through major security bugs doesn't sound very smart to me.

I don't get a vibe that Intel is enjoying this publicity or the presumed replace of those chips. My understanding is that AMD is quite competitive today in the data center.

Re:Intel patches new ME vulnerabilities by frankharv on Sunday July 22, 2018 @11:02PM (#17590292)
The Intel C2xxx Chip was faulty and I wonder if there is more to this story. Like CPU degradation due to heat. Maybe the traces on the CPU just can't hold up to heat. The reason I say this is the top end C2750/C2758 seems to be more at risk then the C2338 dual core. This is unscientific just browsing forums. I think this is heat related.

Wasn't the C2xxx series also an expensive server SOC. Man these guys are fumbling.

[0]https://www.theregister.co.uk/2017/02/06/cisco_intel_decline...

Re:Intel patches new ME vulnerabilities by nebulous1 on Sunday July 22, 2018 @09:34AM (#17586650)
My i7-2600 is still a beast (well, still gong strong anyway). They did the same thing with Meltdown/Spectre fixes.
Re:Intel patches new ME vulnerabilities by NullPrefix on Sunday July 22, 2018 @09:38AM (#17586666)
Grandpa, it's time to upgrade.
Re:Intel patches new ME vulnerabilities by PostOnce on Sunday July 22, 2018 @09:44AM (#17586698)
with an entry-level GPU and slow RAM that works with an i5-2500k, i can play every modern game i have tried on high.

Nothing about me opening a text editor, interpreting most code, or compiling the occasional thing require anywhere near that much power.

For the overwhelming majority, and i really mean overwhelming, there's really no progress or point to upgrading anything except the gpu in the past 7 years or so

in laptops, new stuff uses a LOT less power for the same speed, so there's that I guess.

Re:Intel patches new ME vulnerabilities by opencl on Sunday July 22, 2018 @09:59AM (#17586771)
I upgraded my 2500k last year (to a Ryzen system) and the extra cores are very nice sometimes but honestly the biggest improvement was the fact that I also went from 8GB RAM to 16GB. There were a couple of games that benefited substantially from faster memory (Rise of the Tomb Raider, Fallout 4) but generally not so much the actual CPU performance.
Re:Intel patches new ME vulnerabilities by coaxial on Sunday July 22, 2018 @09:41AM (#17586677)
Why? Because it's been longer than intel would like since parent gave them money?
Re:Intel patches new ME vulnerabilities by bhouston on Sunday July 22, 2018 @10:12AM (#17586839)
If Intel has made currently processes ultra fast recently that wouldn't be an issue, but the Intel Core i7 2700 is actually not that slow. Roughly comparable, at least within 20%, of other 4 core + 4 HT Intel processors.
Re:Intel patches new ME vulnerabilities by NullPrefix on Sunday July 22, 2018 @09:38AM (#17586662)
No real advancement after Sandy Bridge was made. Only incremental 10% with each gen. That means current gen is only 2x as fast when comparing the same lines (i7 to i7). If you can't make new things better, just gimp the old ones, like Spectre/Meltdown.
Re:Intel patches new ME vulnerabilities by close04 on Sunday July 22, 2018 @09:58AM (#17586768)
2 times faster would be quite good actually. Sadly we're barely at 50% faster per core, and that's including the usual 20-30% frequency bump on newer models. Pure IPC improvement is even lower, at maybe 2-5% per generation (~30% total at same frequency, 2nd gen vs. 7th gen).

Yeah, you could argue that doubling the core or thread count doubled performance in selected software but the reality is that for real world use, excluding specific corner cases, the improvement is hard to notice.

A reason to upgrade is to have a newer platform and the features that would bring, definitely not the CPU.

Re:Intel patches new ME vulnerabilities by watersb on Sunday July 22, 2018 @11:44PM (#17590430)
My Ivy Bridge laptop uses twice the power as my Apollo Lake laptop.

Literally 2x.

Re:Intel patches new ME vulnerabilities by NullPrefix on Monday July 23, 2018 @08:44AM (#17592310)
Apollo is Atom, isn't it? So it's not apples to apples. I'm pretty sure there were sub 10W SoC for some years before Ivy bridge.
Re:Intel patches new ME vulnerabilities by watersb on Tuesday July 24, 2018 @06:19AM (#17599630)
Yes, Apollo Lake is an Atom SoC. While I am doing simple web development, performance is about the same. Mostly lacking RAM versus older, Core platforms.

But all-up, Windows 10 at 6 Watts. Including the display, storage, the whole system — or so the performance counters on the battery tell me.

Re:Intel patches new ME vulnerabilities by merb on Sunday July 22, 2018 @10:56AM (#17587064)
well ddr4 is a huge improvement
Re:Intel patches new ME vulnerabilities by Dylan16807 on Sunday July 22, 2018 @02:05PM (#17587966)
If you're memory-starved, yes. A typical quad core is not going to be memory-starved, and the effect is pretty mild compared to the effect of a GPU. Or for non-gaming, it either doesn't matter at all or is 90% about core count.

https://img.purch.com/r/711x457/aHR0cDovL21lZGlhLmJlc3RvZm1p...

Re:Intel patches new ME vulnerabilities by sebazzz on Monday July 23, 2018 @07:21AM (#17591921)
My Dell laptop doesn't have a way to activate it (Latitude) because Dell thought it was an paid feature. I am happy and safe.
Re:Intel patches new ME vulnerabilities by nekocentral on Sunday July 22, 2018 @10:52AM (#17587034)
Guilty, core i3 2120 and not planning on replacing anytime soon
Re:Intel patches new ME vulnerabilities by some_account on Sunday July 22, 2018 @10:18AM (#17586876)
I guess I should not be surprised that the HN community doesn't really seem to care.

Intel put the Management Engine into every CPU with no choice from consumers to opt out. That alone is fairly surprising, since they knew it was a big chance it would have exploits and consumers would have no defense.

But nobody reacts. Nobody cares.

Re:Intel patches new ME vulnerabilities by turblety on Sunday July 22, 2018 @10:50AM (#17587023)
I'm not sure nobody cares, there are a lot of people who do care and (like me) refuse to buy Intel products. I think the problem is there is no other competitor. Both Intel and AMD (or possibly a three letter agency) have colluded to ensure there are locked management engines in all of their products.

Also people just don't understand what the ME actually is. It is surprising the HN community who are mostly technical don't see just how atrocious it really is.

One thing to note however, is I tell my none technical associates there is a second computer in their laptop. It runs software meant to remotely control their computer. They they can not remove it, they can not see what it does, and there's frequently security bugs found in it. When I tell them this I get told I am paranoid and being stupid. However when I ask them to just imagine if it was true, wouldn't it be awful, they mostly agree.

The issue is people really don't want to know the truth. It reminds me constantly of a quote from the matrix:

"Many of them are so injured, so hopelessly dependent on the system, that they will that they will fight to protect it."

Re:Intel patches new ME vulnerabilities by rrdharan on Sunday July 22, 2018 @10:46AM (#17587009)
I'm curious what would you consider to count as an acceptable "reaction" from the HN community?

At any rate I'm unlikely to provide one. Personally I probably won't care until a Snowden-like disclosure that demonstrates exploitation of the ME in a scenario that directly affects me. i.e. I wouldn't be surprised that nation states are exploiting this in targeted fashion, but nation states already have all kinds of ways to get my data in ways that I'm unlikely to be available to defend myself against if I'm targeted.

I'd be more interested in hearing about how ME vulnerabilities are being used in US State-level dragnet surveillance or perhaps to subtly manipulate the population by changing their Google/Twitter/Facebook results or something of that nature. If you find any evidence of that, let me know.

Re:Intel patches new ME vulnerabilities by nine_k on Sunday July 22, 2018 @10:57AM (#17587065)
Imagine: "We, the U-Boot Command, don't care about fears and rumors until an exploit of the Enigma encryption technology is actually demonstrated."

A good exploit is kept as invisible as possible, and when it is publicized, it may already be game over. A Trojan usually takes a lot of measure to stay undetected. Much of the recent crop of router-targeted exploits did not manifest their presence to the users in any way. Even with Snowden revelations, what has been shown was not just illicit mass data collection, but also huge reams of data already illicitly collected.

Re:Intel patches new ME vulnerabilities by Kliment on Sunday July 22, 2018 @11:52AM (#17587311)
I care. I removed ME from mine. I'd prefer to use a competitor but the only viable one is AMD and their equivalent tech is less documented and no known way to disable it exists. Disabling/removing ME is possible for intel stuff so intel is actually the better choice if this is important to you.
Re:Intel patches new ME vulnerabilities by bogomipz on Sunday July 22, 2018 @01:52PM (#17587891)
Might you have some documentation or resources on the procedure for removing/disabling the ME?
Re:Intel patches new ME vulnerabilities by _emacsomancer_ on Sunday July 22, 2018 @02:13PM (#17587999)
Re:Intel patches new ME vulnerabilities by exikyut on Sunday July 22, 2018 @10:09AM (#17586823)
Wow.

The Web really has won.

We have HTTP parsing failures in our CPUs.

Re:Intel patches new ME vulnerabilities by 21 on Sunday July 22, 2018 @11:37AM (#17587246)
I'm waiting for the day where Node.js runs inside the CPU, downloads NPM packages, and then a left-pad happens. Mark my words.
Re:Intel patches new ME vulnerabilities by westmeal on Monday July 23, 2018 @12:31AM (#17590597)
Maybe we'll both get to laugh when we're 90
Re:Intel patches new ME vulnerabilities by ajross on Sunday July 22, 2018 @10:29AM (#17586922)
No, this is a firmware bug. It just happens to be firmware that runs on the ME and not the main cores. The code is stored externally to the CPU along with the BIOS, and looks like it's being patched via a BIOS update.
Re:Intel patches new ME vulnerabilities by flafla2 on Sunday July 22, 2018 @10:55AM (#17587054)
The bug was part of the IME’s built in HTTP server, which is what the parent was alluding to.
Re:Intel patches new ME vulnerabilities by ajross on Sunday July 22, 2018 @05:41PM (#17589070)
Sure, but that's "in our CPUs" in, kinda, exactly the same way that nginx is. It's a microcontroller. It's not like the hardware implemented an HTTP server.
Re:Intel patches new ME vulnerabilities by exikyut on Monday July 23, 2018 @08:43AM (#17592298)
If I just swap the paragraphs in your comment,

> It's not like the hardware implemented an HTTP server.

But yes, yes yes it is.

I don't mean "in our CPUs" in the sense of running nginx. I say "in our CPUs" because

- the Web server is physically inside the CPU die

- you can't remove or change it thanks to code signing, so (to me) it's truly wedged in there

In effect, it's as hardcoded as the electrical circuitry and the transistors are.

Andrew Tannenbaum penned an open letter of surprise and shock because the use of MINIX was an implementation detail ("the licensing works for us, and it's been stared at by tons of professors and a bunch of smart kids for about 20 years, it's good"). Okay, so it's running on 3 little 486-and-a-bit class x86 cores, and it isn't embedded into the main execution pipelines (...yet. I can see that being attractive, something something "software defined ICE").

These details don't change the bigger picture - until someone can break the ME signing infra in a way Intel can't easily fix, and we can disable (or, more ideally, take over/pwn) ME for good, it's as good as mask ROM.

Re:Intel patches new ME vulnerabilities by ajross on Monday July 23, 2018 @10:38AM (#17593057)
> - the Web server is physically inside the CPU die

It's loaded from external storage, and probably runs in external DRAM.

> - you can't remove or change it thanks to code signing, so (to me) it's truly wedged in there

They literally just did, that's what the linked article is about.

> In effect, it's as hardcoded as the electrical circuitry and the transistors are.

If your criteria for hyperbole is the inability of the user to make modifications, then every effective DRM strategy is "as hardcoded as the electrical circuitry and transistors" also.

That's silly. It's a CPU. It runs software. It speaks to devices with drivers. There's no technical meat to your argument.

Re:Intel patches new ME vulnerabilities by exikyut on Tuesday July 24, 2018 @07:59PM (#17605904)
>> - the Web server is physically inside the CPU die

> It's loaded from external storage

No, it's stored on NAND located physically inside the CPU.

> , and probably runs in external DRAM.

It can access all of main memory (and actively uses this ability as part of operations, probably for MMIO communications with UEFI and SMM), but I do think the little 486+-class cores have a bit of their own dedicated RAM on-chip. This makes sense; you don't want MINIX's operation interfering with whatever OS is running, and besides, if you did use main RAM, masking the used pages (with the MMU), so the OS couldn't simply observe/control everything, would honestly leave too much of a visible dent in the system and probably make more of a stink.

>> - you can't remove or change it thanks to code signing, so (to me) it's truly wedged in there

> They literally just did, that's what the linked article is about.

Right. Now to wait and see how long this jailbreak lasts for...

>> In effect, it's as hardcoded as the electrical circuitry and the transistors are.

> If your criteria for hyperbole is the inability of the user to make modifications, then every effective DRM strategy is "as hardcoded as the electrical circuitry and transistors" also.

I'm taking into account the specifics of this particular scenario. I'm aware of other context, but in this case I'm not generalizing. ME updates are signed, and there's currently no complete "perfect" jailbreak, so the effective summarization is "it's locked down".

Considering the specifics of other DRM implementations, well, my favorite DRM is WideVine, since that runs on Linux, there's nothing like HDCP for audio yet, so... https://news.ycombinator.com/item?id=15796420 :D - but see all the replies :(, some DRM is indeed that locked down in practice, with no straightforward recourse.

> That's silly. It's a CPU. It runs software. It speaks to devices with drivers. There's no technical meat to your argument.

Technically you're right, for a strict/narrow definition of "CPU" that describes an abstract bridge between a perfect software environment and the squishy/vague real world. I'm not using that definition. I'm also not looking at Intel products as CPUs here (or, okay, not just CPUs), but as devices that contain a component I literally cannot control, with the exception of some vulnerability PoC code that's already been patched. The established status quo is that I cannot own this part of my hardware, that I'm buying the physical package but relinquishing [control over] some aspect[s] of its operation[s] to the manufacturer['s agenda].

The ME runs Minix, which does use drivers, sure. But that's back to looking at hardware exclusively from the software side of things, which is not the basis of this argument.

Re:Intel patches new ME vulnerabilities by IshKebab on Sunday July 22, 2018 @12:18PM (#17587468)
A lot of microcontrollers have hardware http, DNS, DHCP, etc.
Re:Intel patches new ME vulnerabilities by watersb on Sunday July 22, 2018 @11:52PM (#17590465)
I worked at a place where we designed and rolled out a control system based on HTTP on the microcontroller boards. The non-safety-critical hardware configuration system.

You could have done it with SNMP, but one of the developers got a real simple HTTP server into a smaller runtime, and it simplified the job for writing the front end.

Re:Intel patches new ME vulnerabilities by avuton on Sunday July 22, 2018 @09:44AM (#17586695)
I'm oddly lucky that I based my fanless server off an old Atom platform.
Re:Intel patches new ME vulnerabilities by close04 on Sunday July 22, 2018 @10:06AM (#17586808)
"Luckily" most old Atoms will never get mitigations for Meltdown/Spectre :).

So if you're using an Intel CPU today you'll just have to pick your poison.

Re:Intel patches new ME vulnerabilities by PeCaN on Sunday July 22, 2018 @01:22PM (#17587773)
Luckily, most old Atoms are really simple in-order processors that aren't vulnerable to Meltdown/Spectre.
Re:Intel patches new ME vulnerabilities by nine_k on Sunday July 22, 2018 @10:19AM (#17586882)
Running only trusted code on a server is much simpler than on a desktop / laptop: no Javascript in browser.
Re:Intel patches new ME vulnerabilities by avuton on Sunday July 22, 2018 @10:18AM (#17586871)
I was under the impression that they weren't susceptible.
Re:Intel patches new ME vulnerabilities by close04 on Sunday July 22, 2018 @10:44AM (#17587000)
There's a non-exhaustive list here: https://www.intel.com/content/www/us/en/security-center/advi...

Intel® Atom™ Processor C Series

Intel® Atom™ Processor E Series

Intel® Atom™ Processor A Series

Intel® Atom™ Processor x3 Series

Intel® Atom™ Processor Z Series

This being said, this is the current status for my old Atom N270 (2008): https://imgur.com/a/pbeJ306

Unless the tool is wrong, but I think it was generally marketed as a reliable source. In which case maybe someone can recommend a reliable one to test the vulnerability.

Re:Intel patches new ME vulnerabilities by zzzcpan on Sunday July 22, 2018 @01:33PM (#17587826)
Tools usually just check CPUID and system configuration and don't actually test vulnerabilities. And not necessarily interpreting everything correctly. You can do that without running anything, just checking your OS updates and whether your CPU is out-of-order one, i.e. with speculative execution. N270 isn't and therefore isn't vulnerable.

If you want to truly test speculative vulnerabilities, compile this program: https://github.com/Eugnis/spectre-attack (EDIT: although this one probably won't work on N270, since it uses rdtscp, that it doesn't have, need to find version with just rdtsc)

Re:Intel patches new ME vulnerabilities by zzzcpan on Sunday July 22, 2018 @10:22AM (#17586898)
So, old Atoms are the only ones still usable intel systems and not vulnerable to Meltdown/Spectre/ME.
Re:Intel patches new ME vulnerabilities by namibj on Sunday July 22, 2018 @10:50AM (#17587027)
No, the Xeon Phi "accelerators" are usable too, they are basically 486 cores on modern litography (to allow for higher density/clock speeds), with a vector unit attached to them. I don't know how hard it would be to boot linux on one though...
Re:Intel patches new ME vulnerabilities by detaro on Sunday July 22, 2018 @10:58AM (#17587071)
Only the first generation (X100 model numbers). If I remember right they ship with Linux already, but need a host system to run in of course.
Re:Intel patches new ME vulnerabilities by namibj on Tuesday July 24, 2018 @07:38AM (#17600053)
This host system should be not much more than a PCIe root emulator though. This is the level one can get on an e.g. FPGA with custom logic, which implies that any attempts to insert hardware/firmware level attacks into the actual logic you care about is near impossible to do due to the low-level nature of the custom PCIe implementation.
Re:Intel patches new ME vulnerabilities by bobdole12345 on Sunday July 22, 2018 @12:42PM (#17587598)
They already run linux as their firmware, you can ssh into the cards.
Re:Intel patches new ME vulnerabilities by Filligree on Sunday July 22, 2018 @10:20AM (#17586885)
AMD seems considerably more on top of the security game. As for ME, make sure you avoid any system on which it is enabled.
Re:Intel patches new ME vulnerabilities by monochromatic on Sunday July 22, 2018 @10:36AM (#17586954)
Re:Intel patches new ME vulnerabilities by ekianjo on Sunday July 22, 2018 @11:30AM (#17587205)
That's just because AMD is the underdog and it not as well studied as Intel. Given the same scrutiny I'd wage it would be as bad as Intel.
Re:Intel patches new ME vulnerabilities by geggam on Sunday July 22, 2018 @09:56AM (#17586757)
Every time I am about to upgrade this happens. cpu0: Intel(R) Pentium(R) D CPU 3.00GHz, 2993.01 MHz
Re:Intel patches new ME vulnerabilities by philjohn on Sunday July 22, 2018 @03:29PM (#17588419)
Grab an AMD Ryzen then - you can disable most of the PSP (their ME) via a BIOS setting, and even then, it doesn't do half of the scary stuff ME does.
Re:Intel patches new ME vulnerabilities by 1001101 on Monday July 23, 2018 @09:34AM (#17592591)
A 10 year old buffer overflow? Are they not even running static analysis? If I was working with sensitive info, I would take precautions. I said this the last time the ME got patched: what are the chances that this is the last/only bug?