Re: [FD] 'Rowhammer' - Software-triggered DRAM corruption

2015-03-16 Thread Nick Boyce
On 12 March 2015 at 20:31, Aris Adamantiadis a...@badcode.be wrote: Le 12/03/15 17:00, Nick Boyce a écrit : ... Google was only able to make the attack work on laptops - desktop machines so far remaining unaffected. [I *knew* it was a good idea to hang on to that old Athlon XP desktop :-)]

Re: [FD] 'Rowhammer' - Software-triggered DRAM corruption

2015-03-16 Thread Dirk-Willem van Gulik
On 13 Mar 2015, at 11:32, fulldisclosure fulldisclos...@evolution-hosting.eu wrote: Am 12.03.2015 um 21:31 schrieb Aris Adamantiadis: Le 12/03/15 17:00, Nick Boyce a écrit : Also, this may only affect SODIMMs, not DIMMs, as Google was only able to make the attack work on laptops -

Re: [FD] 'Rowhammer' - Software-triggered DRAM corruption

2015-03-16 Thread fulldisclosure
Am 12.03.2015 um 21:31 schrieb Aris Adamantiadis: Le 12/03/15 17:00, Nick Boyce a écrit : Also, this may only affect SODIMMs, not DIMMs, as Google was only able to make the attack work on laptops - desktop machines so far remaining unaffected. [I *knew* it was a good idea to hang on to that

[FD] 'Rowhammer' - Software-triggered DRAM corruption

2015-03-12 Thread Nick Boyce
(I'm just posting the news - haven't seen this here yet) A team of Google security researchers recently reported on discoveries they have made over the last few months which show it is possible to alter contents of DRAM locations by simply *reading* the contents of neighbouring locations. Using

Re: [FD] 'Rowhammer' - Software-triggered DRAM corruption

2015-03-12 Thread Aris Adamantiadis
Le 12/03/15 17:00, Nick Boyce a écrit : Also, this may only affect SODIMMs, not DIMMs, as Google was only able to make the attack work on laptops - desktop machines so far remaining unaffected. [I *knew* it was a good idea to hang on to that old Athlon XP desktop :-)] There are countless