News for hackers. Stuff that matters.
Re:Meltdown Proof-of-Concept by kodablah on Tuesday January 09, 2018 @12:23PM (#16107816)
This was the GitHub repo mentioned in the meltdown.pdf that was 404'ing until now. We have native Spectre replication code too. What still seems to be elusive is the JS-based Spectre impl (probably waiting at least for Chrome 64, though I confirmed via https://jsfiddle.net/5n6poqjd/ that Chrome seems to have disabled SharedArrayBuffer even before they said they would which wasn't the case a few days ago).
Re:Meltdown Proof-of-Concept by diyseguy on Tuesday January 09, 2018 @12:50PM (#16108078)
This is the closest thing to a javascript implementation I have seen: http://xlab.tencent.com/special/spectre/js/check.js

from: http://xlab.tencent.com/special/spectre/spectre_check.html

Re:Meltdown Proof-of-Concept by kodablah on Tuesday January 09, 2018 @01:06PM (#16108227)
Nice. Reviewing the code, it is as the PDF said where they are just constantly incrementing a val in the shared buffer to get a fairly precise timer. But it seems to be using the timing to determine across 256 indices (99 tries to check) to check cache hits. So just removing this timer is not enough, it just increases the surface area of bytes you have to read and sift through to see if you have other mem? Anyone have a writeup on this?
Re:Meltdown Proof-of-Concept by JonathonW on Tuesday January 09, 2018 @05:51PM (#16110934)
Isn't the high-precision timer required to detect a cache hit or miss-- as in, the side channel being exploited here is in the timing of a cache hit or miss; there's no data leaked directly into Javascript?

That's not to say that removing SharedArrayBuffer (and high-precision performance timers, which were removed a couple years back to mitigate some other timing-related vulnerabilities) is enough to completely eliminate Spectre; there might be other methods that can time accurately enough to reveal information.

(I might be completely wrong here, but this is my current understanding of the situation, at least.)

Re:Meltdown Proof-of-Concept by mwambua on Tuesday January 09, 2018 @01:50PM (#16108659)
Nice tool. Sadly, it reports that my browser (Chromium 63.0.3239.132 with strict site isolation (chrome://flags/#enable-site-per-process) enabled) is vulnerable to Spectre. Do you know if there are any other steps that I can take to secure myself aside from using Firefox?
Re:Meltdown Proof-of-Concept by btb on Tuesday January 09, 2018 @02:05PM (#16108778)
I'm running the same version of Chrome(with site isolation enabled), its reporting "Your browser is NOT VULNERABLE to Spectre" for me. Also in incognito mode with extensions disabled.
Re:Meltdown Proof-of-Concept by mwambua on Tuesday January 09, 2018 @02:09PM (#16108813)
Thanks! It reports the same thing for me too now. I had to enable Top document isolation (chrome://flags/#enable-top-document-isolation) as well.
Re:Meltdown Proof-of-Concept by gadgetoid on Tuesday January 09, 2018 @01:57PM (#16108705)
Found this earlier today via GitHub search: https://github.com/cgvwzq/spectre/blob/master/spectre.js
Re:Meltdown Proof-of-Concept by dingo_bat on Tuesday January 09, 2018 @08:08PM (#16111744)
Interesting that Firefox on my phone is shown vulnerable but Samsung browser is not.