How much/what hardware does the rowhammer DRAM bug affects?

[Cathal Garvey]

I don't actually know the answer to this, but in a summary article on 
the JS exploit they opened by saying part of its beauty was how many 
wonderfully peculiar preconditions were required before it became 
possible. Browser model, JS engine, hardware acceleration options, 
possibly firmwares, and DRAM model/generation/clockspeed.

No reason to be complacent, but the gist was "you probably don't need to 
worry about rowhammer-JS".

Rowhammer itself, OTOH, who knows? :)

On 16/09/15 10:01, Georgi Guninski wrote:
> This is old, but haven't seen it here.
>
> https://googleprojectzero.blogspot.com/2015/03/exploiting-dram-rowhammer-bug-to-gain.html
>
>
> ---
> Rowhammer” is a problem with some recent DRAM devices in which
> repeatedly accessing a row of memory can cause bit flips in adjacent
> rows.
> It was able to use this to gain write access to its own page table, and
> hence gain read-write access to all of physical memory.
> ---
>
> There is POC.
>
> Variant via javascript:
>
> https://github.com/IAIK/rowhammerjs
>
> How much/what hardware does this bug affect?
>

-- 
Scientific Director, IndieBio EU Programme
  Now running in Cork, Ireland May->July
  Learn more at indie.bio and follow along!
Twitter:  @onetruecathal
Phone: +353876363185
miniLock: JjmYYngs7akLZUjkvFkuYdsZ3PyPHSZRBKNm6qTYKZfAM
peerio.com: cathalgarvey