News for hackers. Stuff that matters.
Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by patmcc on Tuesday January 14, 2025 @02:35PM (#42702586)
>>>The problem is that the original DankStartup has a Google account that they create in #1, and Google goes around telling other sites (via Auth) "this is user X from company Y".

Google is telling other sites that it's [email protected] - isn't that true? Isn't this on DankStartup to close down operations cleanly?

Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by cortesoft on Tuesday January 14, 2025 @03:21PM (#42703273)
Sure, but DankStartup failed and doesn’t exist anymore. If I am just a lowly employee, I can’t force the failed startup owners to properly shutdown, and now my payroll information is available to hackers.

What is my remedy?

Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by DrillShopper on Tuesday January 14, 2025 @03:55PM (#42703719)
In a rational world the remedy would be to sue Google for exposing your payroll information.
Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by dragonwriter on Wednesday January 15, 2025 @04:24PM (#42717240)
Google is neither the party holding the payroll information nor the party that chose to make it available on terms that are insecure against loss of control of the domain, why would it be rational for them to be liable?
Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by DrillShopper on Thursday January 16, 2025 @09:37PM (#42733509)
Because they're running the faulty auth
Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by patmcc on Tuesday January 14, 2025 @11:59PM (#42707482)
Probably sue the failed startup owners for negligence?

If DankStartup left all your HR files lying around in their office and the guy who bought it five years later found them, well, DankStartup should have shredded them. It'd sure be nice if the cleaners shredded them for you, but I wouldn't count on it (nor make them liable).

Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by dragonwriter on Wednesday January 15, 2025 @04:21PM (#42717190)
> Probably sue the failed startup owners for negligence

The owners generally aren't liable (assuming or corp or LLC), and if the company would have been liable, that liability probably died with the firm.

Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by grepfru_it on Tuesday January 14, 2025 @03:08PM (#42703099)
Part of my company dissolution process is to renew the domain name for 10 years to prevent exactly this
Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by jedberg on Tuesday January 14, 2025 @04:09PM (#42703893)
Is the hope that this sort of attack is just less useful in 10 years? What happens after 10 years?
Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by stackghost on Tuesday January 14, 2025 @04:49PM (#42704381)
Presumably after 10 years of failing to collect on their invoices, Microsoft would have killed your O365 account, so there's one fewer SaaS account left to log into.
Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by paulddraper on Tuesday January 14, 2025 @05:38PM (#42704925)
Yes
Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by grepfru_it on Friday January 17, 2025 @07:05AM (#42736677)
Common sense would dictat that you have sunset your business by this time.
Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by mansilladev on Tuesday January 14, 2025 @05:47PM (#42704989)
Yes, this. I also use a service to capture all emails (catch all) so that I can detect any loose ends that might have been overlooked. Services like ForwardMX or Cloudflare can do this for you at relatively low (or no) cost.
Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by tsimionescu on Tuesday January 14, 2025 @04:22PM (#42704058)
It's a different [email protected], and in fact a completely different DankStartup.com. Google shouldn't conflate the two.

There are exactly 0 situations where the current behavior is useful. There is no reason whatsoever to have the exact same auth info for two Google accounts that happen to have the same domain.

Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by freedomben on Tuesday January 14, 2025 @06:06PM (#42705162)
Whoever has access to the inbox and account for [email protected] is [email protected]. If Google was being asked if the SSN for bob is 123-45-6789 and they were saying yes, then I would agree that's an issue, but all Google is saying is "this person can authenticate to our services as [email protected]" and that is true.
Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by tsimionescu on Wednesday January 15, 2025 @02:01AM (#42708163)
But the new owner does not have access to the inbox or any other account info of the old [email protected]. They're completely separate accounts, with the same email address. Plus, Google already recognizes that fact, by setting a different value in the "sub" field of the claim it returns (though per the article, it seems that may not work properly).

And legal relations just don't work this way. A person is who they are, and it is that person who has legal access to whatever data was stored in their Slack. Another person who happens to have the same email some time later doesn't have any right whatsoever to that same data. OAuth exists to help secure this type of legal relation, not to establish a completely fictitious identity.

Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by ForHackernews on Wednesday January 15, 2025 @07:16AM (#42710059)
> Google already recognizes that fact, by setting a different value in the "sub" field of the claim it returns

Then Google is doing the right thing. It's incumbent on the relying party to enforce its own authorization policies based on the information the authorization server provides.

Google says, "here's [email protected] <id=n49d0x>", oh here's "here's [email protected] <id=pv82x1d>"

Google can't save consumers from their own negligence.

Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by patmcc on Wednesday January 15, 2025 @11:53AM (#42713459)
So why isn't it on Slack to address this (or not use OAuth, if it can't)? Google doesn't verify the actual legal person behind an email address, whether it's through gmail or google workspace, nor would we want/expect them to.
Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by patmcc on Tuesday January 14, 2025 @11:52PM (#42707447)
>>>It's a different [email protected], and in fact a completely different DankStartup.com. Google shouldn't conflate the two.

Does Google have any reliable way of knowing that?

>>>There are exactly 0 situations where the current behavior is useful. There is no reason whatsoever to have the exact same auth info for two Google accounts that happen to have the same domain.

I have a personal google workspace account with a few domains. At some point I might want to spin one off to be its own (maybe I start a company). But I'd still expect [email protected] to keep working throughout. So that's 1 situation.

Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by tsimionescu on Wednesday January 15, 2025 @02:09AM (#42708198)
> Does Google have any reliable way of knowing that?

Yes, Google knows this is a new Google Workspace account using the same domain as the old one.

> I have a personal google workspace account with a few domains. At some point I might want to spin one off to be its own (maybe I start a company). But I'd still expect [email protected] to keep working throughout. So that's 1 situation.

That should be a separate feature of Google Workspace, where you can transfer an identity, it shouldn't be automatic. And it shouldn't even be tied to the domain name. If you decided that you prefer the domain to be [email protected], you'd still want to have access to the old Slack conversations or whatever. Conversely, if you lost access to the mydomain.com domain (say you forgot to renew it, or some legal entity sued for it because it was their trademark or whatever), I'm certain you wouldn't want the new owners to then have access to your Slack or any other data, just because they have the same domain name.

Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by patmcc on Wednesday January 15, 2025 @11:58AM (#42713548)
>>>Yes, Google knows this is a new Google Workspace account using the same domain as the old one.

I agree it knows that, but it doesn't know:

>>>It's a different [email protected], and in fact a completely different DankStartup.com. Google shouldn't conflate the two.

How should it verify that? Should it? If you buy a domain that was used ten years ago, do you want google to say "well, we can't let you use [email protected], someone used it previously and it may be confusing".

>>>I'm certain you wouldn't want the new owners to then have access to your Slack or any other data, just because they have the same domain name.

Maybe nobody should be using domain name and/or email address as authentication, but that ship has sailed in 100 different ways.

Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by Salgat on Wednesday January 15, 2025 @12:07AM (#42707527)
Login credentials are more than just the email used, and should not be conflated with identity. To be honest I'm surprised google isn't using a uuid tied to the account for the identity given to others, especially since internally google knows and treats it as a separate account that just happens to have the same e-mail. The e-mail should only be used as metadata for contact info.
Re:Millions of Accounts Vulnerable Due to Google's OAuth Flaw by jsnell on Wednesday January 15, 2025 @04:14AM (#42708944)
> To be honest I'm surprised google isn't using a uuid tied to the account for the identity given to others

But they are providing a unique, stable, never reused identifier tied to the account, as has been mentioned a number of times in this thread. It's the "sub" field[0], whose entire purpose is to be the unique identifier for tying the IDP's data to the RP's data.

What they're not doing is to provide that unique id in the "email" field, because the purpose of the email field is to contain the email address. The documentation even specifically tells not to use it as the primary identifier.

> The e-mail should only be used as metadata for contact info

Indeed. But that's up to the relying party. The only way to prevent them from checking the wrong field would be to not provide them the email address at all, even when they're explicitly requesting it.

[0] https://developers.google.com/identity/openid-connect/openid...