4 ms·
But while there are no known cases where Rowhammer attacks have been used in the real world Not on purpose but I'm sure that either it or phenomenon like it ar
by userbinator 5y ago
But while there are no known cases where Rowhammer attacks have been used in the real world
Not on purpose but I'm sure that either it or phenomenon like it are the causes of a lot of odd "glitchy" behaviour that people encounter, because systems are run so close to their limits that there are bound to be cases when they surpass the limits. I remember many years ago discovering that a system which passed the CPU and memory stress tests of the time 100% (ran many days), but would very reliably corrupt a particular .zip file's contents upon extraction; and no other that I could see. Turning down the FSB by 1MHz(!) was enough to make it stable again.
But I remain convinced that Rowhammer is a fundamental defect and all RAM which is susceptible to it should be recalled and replaced. It really says something about the industry when they've managed to convince memory testing tools to treat RH tests as "optional" and "not a real concern, most RAM will show errors" when the discovery first came to light. 26 years ago, Intel offered to recall and replace processors that couldn't divide, after an initial period of reluctance, but only once the bad publicity started. Can RAM manufacturers be coerced into doing the same, and perhaps even go back to pre-Rowhammer process sizes? Sacrificing correctness should never be an option.
(This post made from a 10+-year-old machine containing RAM that is perfectly free of Rowhammer.)
- dannyw 5y agoECC Ram would mitigate some these impacts at least. But yes, it's ridiculous. Some memory sticks I buy get corrupted bits at rated speeds for my memory heavy workloads. Crucial (micron) would always accept the warranty claim, but Corsair has tried rejecting multiple claims saying their memory is designed for gaming. Now I decided to finally pay the xeon tax and go ecc memory. Yes, I know AM4 had "ecc support", but even on asrock motherboards it doesn't necessarily work.
- marcan_42 5y agoThe problem isn't RowHammer, the problem is lack of ECC. This is mostly Intel's fault, as they cripple their consumer CPU lines to disable ECC for market segmentation purposes. The entire premise that we can store tens of gigabytes of information reliably in tiny silicon capacitors without any error detection or correction whatsoever is ludicrous. Every other storage technology uses advanced error correction - NAND Flash, HDDs, optical media, etc. We've been doing this for decades. Even floppies at least had error detection (checksums). All high speed transmission protocols also do error detection and re-transmission, except HDMI (because I guess nobody cares about the odd corrupted pixel). Same for anything going over radio. Once you have ECC, your error rate margin goes up by many orders of magnitude. Worst case these attacks turn into a DoS as ECC fails to correct a badly corrupted word, and most of the time it will just work. Plus you can detect attack attempts as the memory controller will report increased error rates. It's not possible to design modern RAM that is perfectly reliable. That's just physics. We know how to solve this problem. We just aren't doing it because Intel thinks consumers don't deserve reliable RAM. The only other option is doing ECC on-chip in the RAM itself, and that has other efficiency trade-offs which probably make it not worth it, at least not with DDR style interfaces (it might've made sense in an FB-DIMM style world where the memory controller is in the RAM)
- userbinator 5y agoECC is at best a temporary workaround, and at worst an implicit approval of the creation of defective products. It's purpose is to prevent transient bitflips due to cosmic rays and such, not consistently reproducible errors from what is otherwise perfectly normal operation. Plus you can detect attack attempts as the memory controller will report increased error rates. Now you've turned specific access patterns into "attack attempts", and by discriminating against them as such, entirely destroyed a fundamental part of general-purpose computing. What's next, CPUs that are only guaranteed to do certain operations correctly, and everything else is considered an "attack"? That is NOT a direction that we should be heading. Hell fucking no!!! RAM should always hold what was last written to it, under all conditions of software accesses. To expect or imply that anything less is acceptable, is to destroy one of the foundations on which general-purpose computing is built. NAND Flash Where manufacturers are trying to sell 2-4x the capacity with 1/4 to 1/16th of the endurance? That's a rant for another thread... We know how to solve this problem. This problem didn't exist 15 years ago. It only got created because the RAM companies have forsaken correctness, and somehow managed to convince everyone else that it's not their own fault.
- staticassertion 5y ago> Now you've turned specific access patterns into "attack attempts", We already have error correction detection available to us and it's in use today. > RAM should always hold what was last written to it, under all conditions of software accesses. OK? That's what anyone who is advocating for ECC is already advocating for. ECC is error correcting up to 1 bit and error detecting up to 2 bits. The goal is to ensure that the property you've described holds. > It only got created because the RAM companies have forsaken correctness, This problem exists because... physics. Do you actually have a design for RAM that can match today's cell density while somehow providing perfect isolation? Saying this problem didn't exist 15 years ago is like saying that malware didn't impact the abacus - RAM 15 years ago was designed completely differently, and had considerably lower capabilities in terms of storage and latency. And for reference, hamming codes (which back ECC) were created in the 1950s for error correction in punch cards. This is not a new problem. ECC is the existing, obvious solution to this problem, it just wasn't built for this threat - but it's an excellent, proven method for correcting bit flips. Even without being designed to prevent rowhammer it already makes the attack much slower, less likely to succeed, and easier to detect (just monitor for a massive spike in ecc corrections). Trying to design high density RAM that maintains perfect isolation seems pointless. Improving ECC or ECC-like approaches is likely going to be much more effective.
- latch 5y ago> no known cases Is there any way to get a sense for how meaningful this is? Like, is it a pretty sure bet that no attack has happened? Or, if an attack has happened, it's likely been targeted state-sponsored? Or, is it every time you deploy on a multi-tenant host (e.g., ec2), you're playing Russian roulette?
- deleted 5y ago[deleted]
- dahfizz 5y agoCloud hosting (ec2) will use ECC ram on the baremetal hosts, which make this already impractical exploit basically impossible.
- Waterluvian 5y agoChrome gave me a segfault crash message I've never seen before by simply visiting youtube this morning. I thought for a moment what the most likely explanation was, given Chrome has surely seen a boatload of stability testing. It's a sandbox viewing a website. A segfault?! I wonder if it's cosmic rays on my non ECC RAM or some accidental rowhammer moment.
- mvanaltvorst 5y agoRowhammer does not really happen in real life scenarios, because if you access the same block of memory multiple times it usually gets cached in L1, L2 or L3 cache. You really have to try to induce such a magnetic field in RAM. The things you're referring to are probably from other sources of random bit flips, such as cosmic radiation.
- deleted 5y ago[deleted]
- Akronymus 5y ago> ot on purpose but I'm sure that either it or phenomenon like it are the causes of a lot of odd "glitchy" behaviour that people encounter, Transient bugs are some of the worst bugs out there. Erlangs approach of crashing + restarting seems to make sense after all. (I used to think that such cases would not exist at all, but have been proven wrong time and time again. It also can make sense for cases such as dropped connection)