Ask HN: Real-World Breaches from Speculative Execution Vulns?
1–8 of 8 posts
Re: Ask HN: Real-World Breaches from Speculative Execution Vulns?
#2Re: Ask HN: Real-World Breaches from Speculative Execution Vulns?
#3Keep in mind that "breach" here is limited to an information leak . Passwords could be read to achieve a privilege escalation; but a more likely attack would be stealing private keys or other sensitive information. The latter would leave no trace on the target system. So how would you know if your private keys or passwords had been stolen?
Re: Ask HN: Real-World Breaches from Speculative Execution Vulns?
#4Re: Ask HN: Real-World Breaches from Speculative Execution Vulns?
#5I've never seen them in the wild.
Re: Ask HN: Real-World Breaches from Speculative Execution Vulns?
#6Second is that for the most vulnerable attack scenarios, they were mitigated long before the public release of Spectre and Meltdown. The big one was cloud computing - attackers being able to exfiltrate data from VMs running on the same host. Microsoft, Amazon and Google had many months in which to roll out updates to their infrastructure that enhanced VM isolation. Similar for browser vendors, for example Chromium introducing Site Isolation. And operating system developers - mitigations for Windows kernel and Linux were being tested for months before public disclosure.
Re: Ask HN: Real-World Breaches from Speculative Execution Vulns?
#7Re: Ask HN: Real-World Breaches from Speculative Execution Vulns?
#8Keep in mind that "breach" here is limited to an information leak . Passwords could be read to achieve a privilege escalation; but a more likely attack would be stealing private keys or other sensitive information. The latter would leave no trace on the target system. So how would you know if your private keys or passwords had been stolen?
My question is about publicized hacks of any kind, which I’d still call “security breaches”.
And even if something were detected -- say, someone stole a password and then used it to break in, and that break in were detected; or someone set up a phishing webserver that had the real private SSL certificate -- how would you know whether the password or cert was stolen via speculative execution, or whether it was socially engeneered, guessed or brute forced (in the case of a password), leaked by a disgruntled employee, or stolen by traditional hacking methods (in the case of a cert)?
EDIT: If by "publicized hack", you mean the hacker(s) themselves made a public claim about having used speculative execution, then no, I haven't personally heard of such an instance.