5 ms·
Has Google the best security team in the world? It seems like Google security is in a complete different league. I cannot imagine how this impacts companies han
by wslh 9y ago
Has Google the best security team in the world? It seems like Google security is in a complete different league. I cannot imagine how this impacts companies handling fiat money or cryptocurrencies in the cloud like Coinbase in AWS.
- ebikelaw 9y agoI can't imagine better marketing for cloud services than making it as clear as you can that the world is a very dangerous place for computers and if you don't have a crack team of hundreds of battle-hardened security engineers then you have no business hooking your computers up to the internet.
- walterbell 9y agoIf true, how are edge computers going to connect to the cloud?
- jopsen 9y agoHmm, or maybe it's a reason to go with bare-metal providers :)
- snowwrestler 9y agoThe irony here is that a good ol' dedicated hardware web server is far less susceptible to Meltdown or Spectre than Google Cloud, because only your code is running on the CPUs. I predict tonight's disclosures will lead to an uptick in interest in running websites on dedicated hardware, like we did back at the turn of the century.
- tanilama 9y ago> Spectre Spectre doesn't really care if it is cloud or bare metal. They are equally vulnerable unless disconnected from internet.
- Godel_unicode 9y agoPretty hard to have a neighbor vm execute Spectre on your same physical server if you have dedicated hardware. Add in that Spectre specifically is a js bug so in order to be vulnerable your server would need to execute untrusted JavaScript and I think we can assume the threat surface of this specific bug is smaller outside the cloud...
- cthalupa 9y agoI don't think you understand the bug here. 1) https://spectreattack.com/ https://spectreattack.com/: "Spectre tricks other applications into accessing arbitrary locations in their memory. " Spectre does not let you execute code in another guest 2) Spectre is not javascript specific. I am not sure why you think it is, beyond the fact a PoC was written in js
- Godel_unicode 9y agoI don't think you understand my point. You should reread my post, especially the first sentence. It's first and alone for a reason; not sharing hardware is an effective mitigation against vulnerabilities in shared hardware. Obviously it's not just a js bug, there are other PoCs in other languages. I never said anything about executing code in another guest, not sure where you got that from.
- TickleSteve 9y agoSpectre is exploitable from processes, not just containers.... containers are equivalent to processes from it's point-of-view as the kernel is shared. So... you may be able to go native to avoid having neighbours, but this does not prevent other processes exploiting your process. To do that you need to prevent any downloadable code from running. This of course is possible and is the entire reason why the ARM document explains that most embedded systems are not affected due to the fact that they will not download and execute code (of any form).
- oh-kumudo 9y agoCloud services will benefit from this greatly. Spectre occurs no matter you are in cloud or not, while cloud companies can advertise themselves to help customers proactively to mitigate such risks.
- enneff 9y agoI don't know how you would evaluate such a thing as "best security team," but Project Zero certainly attracts a high calibre of security expert. If you're into breaking things, why wouldn't you want to break things with other bright people and the support of a massive corporation?
- jacksmith21006 9y agoHow about based on how many of the serious issues are found by Google. It has been one after another.
- Godel_unicode 9y agoThey're definitely world class, but they're also loud about it. Consider that other teams perhaps have a different model. For instance, Microsoft's internal team surely finds lots of clever bugs that never get talked about in Microsoft products.
- ForHackernews 9y agoI assume the NSA finds and quietly stockpiles some very clever vulnerabilities, too.
- rurban 9y agoDid you forget the Technical University of Graz students who came up with rowhammer and KAISER in the first hand?
- wslh 9y agoNot really, they are mentioned in the article. What is fascinating is the number of discoveries by the Google team. The Wikipedia page has a summary of the prominent ones: https://en.wikipedia.org/wiki/Project_Zero_(Google) https://en.wikipedia.org/wiki/Project_Zero_(Google) these are not bugs in obscure pieces of software but on major services and operating systems.
- rurban 9y agoCome on, Google completely "forgets" to mention the others, whilst the others do mention Google who detected it independently. And then look who wrote the papers, exploits and patches.
- kps 9y ago> Come on, Google completely "forgets" to mention the others Err… fourth paragraph: > Before the issues described here were publicly disclosed, Daniel Gruss, Moritz Lipp, Yuval Yarom, Paul Kocher, Daniel Genkin, Michael Schwarz, Mike Hamburg, Stefan Mangard, Thomas Prescher and Werner Haas also reported them; their [writeups/blogposts/paper drafts] are at: Spectre (variants 1 and 2) Meltdown (variant 3)
- willsr 9y agoYuval Yarom's contribution (Flush+Reload) seems quite understated, considering how important it is to the attack.
- gervase 9y agoProject Zero is very well known for things exactly like this. Partially, it's because they are incredibly talented, but there are also talented people in academia and in other security consultancies. The biggest difference with Project Zero is that their primary [0] goal is altruistic: find vulnerabilities, and let people who can fix them know (vs publishing papers, securing paying clients, auctioning zero-days, etc), in the interests of making the internet and computing as a whole a safer place. [0] Their secondary goals are to protect Google products and services, and to provide excellent PR in line with what we're discussing right here.
- kzrdude 9y agoHm 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! :-)
- ehsankia 9y agoYes 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.
- oh_sigh 9y agoHow 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
- make3 9y agoDiscovering a vulnerability is not creating it. A vulnerability exists even if it was not publicly disclosed. There were probably other people already exploiting it.
- tanilama 9y agoImagine the law suit if Google fails to detect this....
- deleted 9y ago[deleted]
- dzhiurgis 9y agoI wonder how much of it relates to their mastery in data science. I keep wondering if they got some “””AI””” fuzzer that helps them a ton? Plus tons of compute power to spend (remember SHA-256 clash they found “just because”?)
- Ar-Curunir 9y agoNo collision has been found in SHA-256. SHA-1 is the broken hash function