12 ms·
The Next Vulnerability: Looking Back on Meltdown and Spectre One Year Later
- deepnotderp 8y agoThe basics of the spectre exploit were discoverable 20 years ago and run deep, to the very core of branch speculation. This is nothing but marketing for risc-v and rambus, there's no magic in risc-v that prevents spectre except that the ecosystem is so primitive that they barely have any speculative processors... We could have found the spectre exploit 20 years ago. To me, the fact that we didn't until now is maybe the most interesting thing.
- userbinator 8y agoTo me, the fact that we didn't until now is maybe the most interesting thing. I suspect it's because there was still plenty of far simpler and more obvious exploits to look at.
- ufo 8y agoI think one of the reasons is that nowadays we run a lot more untrusted code on top of our hardware, due to things like Javascript and virtualization. Meltdown and Spectre would not be as dangerous 20 years ago.
- blattimwind 8y ago> The basics of the spectre exploit were discoverable 20 years ago and run deep, to the very core of branch speculation. Some aspects of these were known 20 years ago. http://www.cse.psu.edu/~trj1/cse543-f06/papers/vax_vmm.pdf http://www.cse.psu.edu/~trj1/cse543-f06/papers/vax_vmm.pdf section VI.E)
- segfaultbuserr 8y ago> To me, the fact that we didn't until now is maybe the most interesting thing. Back then, people were smashing the stack for fun and profit. Think about it! Executable stack! No canary! No ASLR! Can't be more fun.
- saagarjha 8y ago> These challenges are going away as chipmakers and innovators collectively leverage open-source to develop better solutions and reduce time-to-market. The open source RISC-V architecture is particularly notable for its availability of unencumbered reference implementations and compiler/software support. As a result, RISC-V greatly reduces the amount of ancillary work required for a processor security project, allowing design teams to move more quickly and focus on areas of innovation – including security. Is this a thing? I have not heard of anyone working on trying to replace x86 with RISC-V because of Spectre…
- tyingq 8y agoIt probably switched a few orders from Intel to AMD, where the performance hit of the Intel patches vs the AMD ones changed the performance/$ enough. But probably nothing of enough volume to be notable. Risc-V would be unlikely, since there's not yet real server class silicon.
- ivankolev 8y agoI feel uneasy giving up general purpose computing in the name of security. Can't we have both?
- tomxor 8y agoYes but at a performance cost. I _think_ general purpose scalar processors lack any of the timing vulnerability since they almost literally do one thing at a time. But you are winding back the performance clock 1-2 decades - that's not to say they are unusable, for instance the arm core in the pi zero is scalar... but I doubt there is any modern desktop x86 equivalent without speculative execution.
- blattimwind 8y agoThat ARM11 core is actually partially out of order (i.e. it issues in order, but permits out of order completion of independent insns) and has branch prediction.
- gpderetta 8y agoMore like 4 decades. OoO itself is about three decades.
- vardump 8y agoYup. OoO is a thing from the mid-nineties for us mere mortals. CPUs like Pentium Pro and AMD K5. Of course the first out-of-order CPU is way older CDC 6600, back from 1964. MIPS R2000 from 1986 could do simple form of speculative execution.
- AnIdiotOnTheNet 8y agoApparently not. The security twonks of the world would prefer we all get locked in cages and just consume the content we're fed (slowly as it passes through a hundred layers of abstraction each doing their own bounds checks and the likes). Specter and Meltdown are a great example of this, the community went ape over the whole thing introducing all sorts of slow-your-shit-down mitigations with a lot of people even suggesting that maybe we should ditch speculative execution entirely, for what? Because now there's a relatively high-effort way someone could exfiltrate data from my desktop via a browser? The only people who should have cared about Specter and Meltdown are hosting companies and people working in intelligence, and I would hope the latter have more reliable security practices that already take into account the possibility of things like Specter and Meltdown before they're even known about.
- mehrdadn 8y agoHow many people's computers are known to have gotten hacked via Meltdown or Spectre?
- mikeash 8y agoHow would you know? It allows reading privileged data without actually taking over privileged processes, and wouldn’t leave behind any signs of what happened.
- gizmo686 8y agoNot nessaserilly no signs. It involves rep3atadly triggering the error path with specifically constructed values. This could easily leave behind traces in the log from which it can be infered that there was a spectre attack (of course, determining what attack was being conducted, or its succeslevel and information exfiltrated is still difficult)
- pmoriarty 8y agoIt really would depend on what they did and how they did it. If the "privileged data" they read was, say, the root password which they used to gain root access and then started snooping around the system as root or modifying parts of the filesystem, that could be easily detected. If the exploit itself was performed over the network or if the privileged data they read was transferred over the network, that might also be detected, depending on how it was sent and where it was sent to. If they tried to launch attacks or probes from the exploited system they could be detected at well. Network intrusion detection systems and host detection intrusion systems could both help here.
- pdimitar 8y agoI view the current situation as a good time to invent 32+ core CPUs with less fancy features like all speculative execution or branch prediction (at least not to the extent which made Spectre/Meltdown possible anyway). And a good time for a next-gen kernel to emerge that can make use of several kernel-reserved cores and with better preemptive scheduling overall. Not a hardware guy or a driver programmer but I believe this area stands to get some innovation.
- gpderetta 8y agoWe have today 32+ cores CPUs with minimal or no branch prediction and speculation. They work spectacularly well on some specific workloads but are terrible for general purpose computation. They are called GPUs. Speculation and branch prediction is not going away. On the contrary is going to get more and more sophisticated. What needs to die is the belief that you can rely on just software (i.e. memory safety) for isolation between trusted and untrusted code[1]. [1] Yes, meltdown bypasses hardware protection, but that's an intel specific fuck up, not inherent issue with speculation.
- twtw 8y ago> What needs to die is the belief that you can rely on just software (i.e. memory safety) for isolation between trusted and untrusted code[1]. I don't understand how you came to this conclusion. How does spectre indicate that you can't rely on software for isolation? > meltdown bypasses hardware protection, but that's Intel specific It's not Intel specific. Certain ARM and POWER architectures are also vulnerable. Spectre bypasses hardware protections too, just in a more subtle way.
- gizmo686 8y agoThe idea behind spectre is that speculative execution bypasses software protections. Given if f(A) B else C, one cannot safely assume that B only gets executed when A resolves to true. It is not reasonable to expect programmers to produce safe code in an environment where they have to doubt if statements. This could be solved without any major overhauls in hardware, by just updating it to make speculative execution actually speculative and not commit any side effects until it knows it went down the correct branch.
- childintime 8y agoWhat strikes me the most is that the state of the art in CPU architecture is immune to Spectre and Meltdown, yet it isn't once mentioned. Makes the article sounds like Intel funded stuttering.
- roblabla 8y agoCan you expand on which CPU exactly you are talking to? I'm genuinely curious. From what I've seen, every major high-end CPU architecture is affected, because they all rely on speculation. Of course, some low-end CPUs (such as ARM Cortex-M cores) don't have speculation, so they aren't vulnerable. But on the high-performance front, I haven't seen a credible alternative that wasn't vulnerable to speculative execution side-channels. Which one am I missing?
- twtw 8y agoGiven the phrase "Intel funded" 'childintime is probably confused and thinks AMD Zen is not vulnerable.
- wlesieutre 8y agoMeltdown IIRC didn’t affect AMD processors, but Spectre was pretty much across the board.
- childintime 8y agoIntel is under threat, not only from AMD, but from the end of the x86 era. Of course they need to protect their current bread and butter, but AMD isn't their only worry. Far from it.
- childintime 8y agoExactly, the low end isn't vulnerable, nor is the the Mill architecture on the high end (see millcomputing.com). The Mill isn't silicon yet, but the architecture is sound (and of extreme beauty). It is an architecture for the Intel sized out there though. The Mill makes the current OOO look bad (Intel, AMD, others). It is striking to see that "experts", on this page and the writer of the article, act as if it didn't exist. The Mill can save Intel, or destroy it, Intel decides that. The pos-x86 nears and time is running out. Intel needs a new architecture and RISC-V is only part of the answer.