Discussion in 'Article Discussion' started by bit-tech, 27 Jul 2018.
Holy Grandmother-of-All-Vulnerabilities, how?! How do you read memory contents over the network?
Probably with quite a lot of luck I would imagine, surely address space randomisation means that data rarely gets stored in the same place twice?
I refer you to Section 5.2 of the linked paper, 'Remotely Breaking ASLR [Address Space Layout Randomisation] on the Target System.'
It is explained at the bottom:
The basic access restrictions which are used as a foundation to build security on have been swallowed by a sink hole named Spectre and not installing the updates to plug that hole is about as responsible as announcing on facebook that you will be on holiday next week and that the key is under the door mat.
I'd feel more secure if Asus had a more recent bios than 2016
Well of course I didn't read the paper silly!
So you'd still need a lot of luck.... no? And leaking at a rate of 15 bits per hour?
The main upshot of the discovery of SPECTRE class attacks is to add one more thing you need to consider when hardening your software (alongside "don't try and read from empty buffers" and "don't try and write to full buffers"). Removing Speculative Execution from CPUs is about as likely as removing internal caches. You can technically do without it, but you won't like it.
As hilarious as that is, the pedant in me insists on pointing out that you can have branches without speculation. The 486 that Doom targeted was such a processor.
So it will indeed be devastating to performance, but more like fifty percent than fifty-thousand percent.
But, but ... I'm only leaving for vacation the week after?!
Separate names with a comma.