Nethammer: Inducing Rowhammer Faults Through Network Requests
1–10 of 19 posts
Re: Nethammer: Inducing Rowhammer Faults Through Network Requests
#2It’s about time Intel offers consumers ECC RAM support.
Re: Nethammer: Inducing Rowhammer Faults Through Network Requests
#3How is this different exactly from Throwhammer?
Re: Nethammer: Inducing Rowhammer Faults Through Network Requests
#4It’s about time Intel offers consumers ECC RAM support.
[deleted]
Re: Nethammer: Inducing Rowhammer Faults Through Network Requests
#5It’s about time Intel offers consumers ECC RAM support.
While it won't necessarily help you with this, AMD has support in all Zen CPUs, not just the EPYC server series.
Re: Nethammer: Inducing Rowhammer Faults Through Network Requests
#6[deleted]
Re: Nethammer: Inducing Rowhammer Faults Through Network Requests
#7It’s about time Intel offers consumers ECC RAM support.
ECC wont help, you need row access counters(target row refresh/TRR) directly in ram chips, or in memory controller. With switch to DDR4 JEDEC had a chance of standardizing those mitigations, but that would cost additional cents per chip, cant have that!
Re: Nethammer: Inducing Rowhammer Faults Through Network Requests
#8How is this different exactly from Throwhammer?
> Throwhammer works by registering a large amount of memory space called a buffer on the network card of the targeted device. [1]
> Nethammer is the first truly remote Rowhammer attack, without a single attacker-controlled line of code on the targeted system. Systems that use uncached memory or flush instructions while handling network requests, e.g., for interaction with the network device, can be attacked using Nethammer. Other systems can still be attacked if they are protected with quality-of-service techniques like Intel CAT. We demonstrate that the frequency of the cache misses is in all three cases high enough to induce bit flips. [2]
[1]: https://arstechnica.com/information-technology/2018/05/attac...
Re: Nethammer: Inducing Rowhammer Faults Through Network Requests
#9How is this different exactly from Throwhammer?
Looks like this doesn’t depend on direct memory access. Judging from the devices, it’ll also work at lower speeds, whereas throwhammer requires multi-gbps.
Re: Nethammer: Inducing Rowhammer Faults Through Network Requests
#10How is this different exactly from Throwhammer?
Throwhammer: > 9.375 million packets per second
Nethammer: > 1 024 000 packets per second over a 500 Mbit/s connection ......Hence, we conclude that in theory...
Both currently at best lead to server crash, and are highly impractical.