News for hackers. Stuff that matters.
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.