3 ms·
I think the biggest tell here was that Google had discussed disclosing it, and chose not to out of fear of regulation and bad press. This wasn't an everyday int
by ocdtrekkie 8y ago
I think the biggest tell here was that Google had discussed disclosing it, and chose not to out of fear of regulation and bad press. This wasn't an everyday internal vulnerability. And they have no proof it wasn't used. But they chose to keep it secret specifically because they were afraid of the backlash, and the fact that it would demonstrate their security wasn't significantly different from Facebook's, it was just that they had a vastly less successful product.
Their decision wasn't about what was best for users, it was about what they thought they could get away with. I'm not shocked Congress is interested in that, because the memo is far more condemning than anything about the actual bug.
As an additional note, we can't rely on Ron Wyden to keep Google in check: Google is one of his larger sponsors, spending somewhere around $20,000 a year on him.
- tptacek 8y agoCompanies find RCE and SQLI, fix them, don't conduct gigantic forensics investigations to determine if they'd ever been exploited, and get on with their lives. It happens routinely. What's so interesting about this bug? Did you read the details about it? I wasn't kidding when I called it a sev:low.
- ocdtrekkie 8y agoI don't think people at Google would agree with that characterization, given that they decided to couple it's disclosure with shutting down the whole product. How would you characterize this versus the data leak used by Cambridge Analytica, if you remove the difference in the scale of product users and developers building on the API? Being able to scrape a lot of API data that users explicitly defined as private is a pretty big deal, especially when you consider that Google pretty much forced G+ integration on everyone in the first place, causing them to have accounts they might not even want.
- tptacek 8y agoFor starters, the Cambridge Analytica leak was vastly more impactful than this one, and is known to have been actually exploited? I feel in this thread sort of like how I do in those bug bounty threads where someone is trying to convince me that a logout CSRF should merit a $10,000 payout because a competitor could use it to make a UX experience worse and then shift all the customers to their product and after all Google is such a huge company they shouldn't have CSRF at all and $10,000 is a drop in the bucket. I mean that's not what you're saying but I feel like we're playing Six Degrees Of Kevin Bacon the same way to get from this very marginal bug that they themselves found and fixed to "this merits federal legislative attention."
- asaph 8y ago> ...they decided to couple it's disclosure with shutting down the whole product. Let's not pretend the product was shut down because of this bug. Google Plus was a failed product. This security issue was just a convenient event to which they chose to attach the news. Google's own words on the matter: > This review crystallized what we’ve known for a while: that while our engineering teams have put a lot of effort and dedication into building Google+ over the years, it has not achieved broad consumer or developer adoption, and has seen limited user interaction with apps. The consumer version of Google+ currently has low usage and engagement: 90 percent of Google+ user sessions are less than five seconds.[0] [0] https://www.blog.google/technology/safety-security/project-strobe/ https://www.blog.google/technology/safety-security/project-s...
- ocdtrekkie 8y agoOh, no doubt G+ was a failure. And that's coming from someone who was with it since its launch and still uses it today. But it was closed due to this bug and the drama surrounding it. It wasn't "convenient" to announce closure alongside the bug, the bug actually became much more widely discussed because it was attached to a product shutdown. I can't imagine anyone at Google wanted this to go down that way, it would've been better to quietly shutter it at a different time. But the Wall Street Journal announced it, as part of the memo that they got internally. So Google had to announce it at the same time in the same post, and it was definitely the cause of the product shutdown.
- UncleEntity 8y ago> How would you characterize this versus the data leak used by Cambridge Analytica... That wasn't a leak as much as misusing data that FB happily gave out to anyone who asked -- which FB "disclosed" to great fanfare during the Obama presidential run to show how they could be leveraged for more than looking at pictures of your former college roommate's cat.