Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

People are focusing too much on the exact specific attack shown here: Deduplication, modifying a public key, etc. (And proposing solutions like turning off deduplicaiton, checksum, etc.)

But that's just this attack - the fact that they have that much control over memory means there are FAR FAR FAR more possible attacks.

If you can control memory to that level then you are limited only by your imagination.

The only mitigation I can think of at the moment is ECC memory. And shame on Intel for only supporting that on Xeon.



What can you do to attack other VMs if you don't have shared memory with them?


depends, do they run node? because there were successful javascript rowhammer implementations demonstrated


If you control memory vs. if you control your memory. This does not give you general purpose access.


That used to be a point in AMD's favor for their desktop CPUs.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: