News for hackers. Stuff that matters.

A comment on Reading privileged memory with a side-channel. Parent comment

Re:Reading privileged memory with a side-channel by kzrdude on Wednesday January 03, 2018 @07:35PM (#16066900)
Hm that's tricky. These awesome findings didn't exactly provide net value for google, not even on the not so short term (next 10 years?). They've created a large problem for Google! :-)
[ Parent | on HN ]
Re:Reading privileged memory with a side-channel by ehsankia on Wednesday January 03, 2018 @07:50PM (#16066986)
Yes and no. The cost of some malicious party figuring it out and using it on Google would potentially been far greater than anything this could cost.
[ Parent | on HN ]
Re:Reading privileged memory with a side-channel by oh_sigh on Wednesday January 03, 2018 @07:51PM (#16066994)
How much value would be destroyed if black hats discovered the bug first and people started discovering that information from their Google cloud VMs was getting leaked?

Sure, Google could just patch themselves, but the information to recreate the issue would surely be leaked by a xoogler, since it only takes a single sentence describing the vuln for a competent sec team to recreate it

[ Parent | on HN ]
Re:Reading privileged memory with a side-channel by make3 on Wednesday January 03, 2018 @08:24PM (#16067202)
Discovering a vulnerability is not creating it. A vulnerability exists even if it was not publicly disclosed. There were probably other people already exploiting it.
[ Parent | on HN ]
Re:Reading privileged memory with a side-channel by tanilama on Wednesday January 03, 2018 @09:37PM (#16067540)
Imagine the law suit if Google fails to detect this....
[ Parent | on HN ]