News for hackers. Stuff that matters.

A comment on More Intel speculative execution vulnerabilities. Parent comment

Re:More Intel speculative execution vulnerabilities by MiroF on Wednesday November 13, 2019 @09:37AM (#21524542)
> There have been more Chrome/Firefox 0-days than speculative execution vulnerabilities exploitable in Javascript (0).

sure dude, sure

[ Parent | on HN ]
Re:More Intel speculative execution vulnerabilities by scandinavian on Wednesday November 13, 2019 @09:51AM (#21524720)
Chrome: CVE-2019-13720, CVE-2019-5786 Firefox: CVE-2019-11707/CVE-2019-11708

Your turn. Link the speculative execution 0days.

[ Parent | on HN ]
Re:More Intel speculative execution vulnerabilities by MiroF on Thursday November 14, 2019 @09:07AM (#21535412)
Here's an example of post-mitigation reading of protected memory using Javascript and Spectre https://alephsecurity.com/2018/06/26/spectre-browser-query-c...

I think it's just silly that you would rely on browser mitigations like disabling high precision timers when that's obviously just a hack.

[ Parent | on HN ]
Re:More Intel speculative execution vulnerabilities by scandinavian on Thursday November 14, 2019 @11:54AM (#21536955)
As is said in the PoC, it does not bypass index masking and site-isolation. They read data already available to the code they are executing. They did show that the timer resolution mitigation is not 100% effective, which is well known and why it is not the only mitigation.

That's not a speculative execution browser 0day, as it doesn't work in updated browsers and it never has (or I guess it works if you want to leak data you could just console.log). Could you post an actual 0day instead?

[ Parent | on HN ]