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.
[ Parent
| on HN ]
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.