rowhammer-test

> If you have a process running on your machine can it use this to get root? Read Keys? Yes. There's a BlackHat talk on that[1]. DoS is a big issue on shared hardware too. You can crash other processes, the kernel and the hypervisor. > And if your flipping your process's memory for that long, what are the chances you are next to sensitive memory for another process? You don't need to leave it up to chance. There are apparently ways you can control it and of course you can just spray everything. 1. https://www.blackhat.com/docs/us-15/materials/us-15-Seaborn-... 2. https://github.com/google/rowhammer-test/blob/master/rowhamm...

It's really not that hard [1] and can be used relatively easily for DoS. Privilege escalation with it is beyond me but I'm sure someone can come up with more reliable ways of exploiting it. 1. https://github.com/google/rowhammer-test

Is it simple? From what I understand it is still not clear how Rowhammer is physically possible. If you don't know how it's possible, then current manufacturers may not know how to create good memory. We don't get everything in physics yet and it's affecting our ability to make good memory chips that are secure. One possible explanation of how it is possible, the parasitic coupling effect: https://github.com/google/rowhammer-test/blob/master/docs/re...

Using something like https://github.com/google/rowhammer-test tl;dr: You check. Allocate some memory and hammer it. If you detect flips, step 1 is complete.

You may wish to try both single- and double-sided hammering. If you hit the right row size it is significantly more effective: https://github.com/google/rowhammer-test/blob/master/double_...

Seems like my Macbook Air 2014 is not affected (with a high probability) here's the test: https://github.com/google/rowhammer-test