16 ms·
Tell HN: Google Cloud lets anyone add you to a project without your permission
Recently, a company in Kenya (which I have never heard or nor have any association with) added me to their Google Cloud project without my permission. At first, I thought I had mistakenly accepted an invite to their project. However, I swore that wasn’t the case. To test my theory, I tried creating an empty project and invited my other Google account to it. I discovered that Google Cloud lets you add ANY individual or company email (even at companies you aren't affiliated with) to a project without getting their permission or notifying them. Google doesn’t even send an email asking you to accept the invitation. It just adds you automatically without telling you. The end result is you can quite literally just type in any Google Cloud account (including accounts at companies you don't work at) and associate it with your project without them ever knowing.
The worst part is that you can’t leave the project after you’re added. Google requires the project owner remove you. They provide no way to remove yourself. I’ve tried contacting the company that added me but they’ve not responded to my requests.
I also tried contacting Google support and they’ve been less than helpful. At first, they thought that my account was hacked. I pointed out that this was not due to a hack, but due to Google’s faulty invite system. They responded back and said they didn’t see any association between my email and the project. So they listed the case as resolved and said they couldn’t discuss any further details about the project. This is despite the fact the unwanted project still appears on my GCP dashboard. I suspect they didn’t see any association because they were just checking the projects owned by my account and not checking projects I’ve been added to.
This whole situation seems like a recipe for unwanted spam since you can be added to projects without permission and can’t ever remove yourself. My biggest fear is if that company uses the project to do something malicious then my account might be banned by association. This could also be used in other ways. E.G. you could flood a competing startup's cloud dashboard with hundreds of bogus projects. You could even use it to get someone in trouble by adding them to a project that's doing illegal stuff (e.g. hosting illegal content). If this was limited to adding people within your GCP/GSuite this would be a minor issue because I doubt your coworker is going to use GCP to spam you / get you in trouble. However, the ability to add anyone and everyone outside of your GCP/GSuite makes this a huge issue in terms of spam / safety. Overall, this is a major oversight on Google’s side and is a huge security, privacy, and spam risk.
To date, I’ve still been unable to get any help from Google to resolve this issue. If there’s any Googlers willing to help, I would be extremely grateful.
- thesuperbigfrog 4y agoIdea: (never used Google Cloud, no idea of possible impediments) 1. Create throwaway account 2. Create throwaway project using throwaway account 3. Find emails of possible Googlers using public bug tracker 4. Add Googlers' emails to throwaway project 5. Post messages to throwaway project describing the problem 6. Hopefully Googlers understand the issue and can forward the issue to get it resolved
- deleted 4y ago[deleted]
- toast0 4y ago7. Throwaway Google account gets locked for ToS (adding people without their permission) 8. Associated real Google accounts get locked for being associated with throwaway (unless you have really good OpSec) Might be worth a post on their bug bounty program though, assuming GCP is in scope https://bughunters.google.com/ https://bughunters.google.com/
- Ephil012 4y agoThat’s a great idea. I’ll try reporting it on their bug bounty Edit: Reported it
- 015a 4y agoIdea: 1. Create a throwaway account. 2. Add a bunch of professional developers' at big companies email addresses to the account. Just shoot in the dark: johnanderson@google.com, mikejohnson@airbnb.com, wandamaximov@apple.com, throw in a couple common email aliases as well like developers@twitter.com or mobileteam@airbnb.com 3. Publish a bunch of apps to the play store which clearly breaks their app store policies 4. Google has been known to automatically network-ban associated accounts and their play store apps if a play store account is found in violation of their policies.
- gpm 4y agoI'm sure this isn't a serious suggestion anyways... but if you were going to be malicious like this you ought to not include google.com accounts. They're likely treated differently. Also, harvesting actual emails from github is really easy.