Okay, I should've shouted this earlier. THE AMD VULNERABILITIES THAT JUST CAME OUT HAVE NOTHING WHATSO-FUCKING-EVER TO DO WITH MELTDOWN/SPECTRE IN SCOPE, DANGER, OR APPLICABILITY. ANY COMPARISONS DEMONSTRATE A COMPLETE LACK OF UNDERSTANDING AND A FAILURE AT TECH JOURNALISM.
-
Show this thread
-
Or to elaborate further: TO EXPLOIT MELTDOWN YOU NEED SOME JAVASCRIPT ON A WEBSITE. TO EXPLOIT THIS FIRMWARE STUFF YOU NEED KERNEL MODE CODE EXECUTION. LEARN THE FUCKING DIFFERENCE.
3 replies 25 retweets 74 likesShow this thread -
Replying to @marcan42
Has someone really discovered a way to exploit Meltdown from a browser? How's the exception being controlled?
1 reply 0 retweets 0 likes -
Replying to @slpnix
Same as Spectre. You wrap it in a mispredicted branch (out of bounds access). I'm not aware of any public PoCs but I believe private ones exist.
1 reply 0 retweets 0 likes -
Replying to @marcan42
In Spectre there's no need for exceptions, you're directly (same process) or indirectly (syscall and HT siblings) mistraining the indirect branch predictor. Meltdown seems quite hard (impossible?) to exploit for JS, but I maybe wrong.
1 reply 0 retweets 0 likes
Spectre is two flaws, because the morons who named it mixed together two unrelated vulns. I'm talking about GPZ Variant 1, which is about direct branch misprediction. You can use the same technique to speculate through and recover from the exception.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.