New analysis has pulled again the curtain on a “deficiency” in Google’s “Sign in with Google” authentication move that exploits a quirk in area possession to realize entry to delicate information.
“Google’s OAuth login doesn’t protect against someone purchasing a failed startup’s domain and using it to re-create email accounts for former employees,” Truffle Safety co-founder and CEO Dylan Ayrey stated in a Monday report.
“And while you can’t access old email data, you can use those accounts to log into all the different SaaS products that the organization used.”
The San Francisco-based firm stated the difficulty has the potential to place thousands and thousands of American customers’ information in danger just by buying a defunct area related to a failed startup and gaining unauthorized entry to previous worker accounts associated to varied purposes like OpenAI ChatGPT, Slack, Notion, Zoom, and even HR programs.
“The most sensitive accounts included HR systems, which contained tax documents, pay stubs, insurance information, social security numbers, and more,” Ayrey stated. “Interview platforms also contained sensitive information about candidate feedback, offers, and rejections.”
OAuth, quick for open authorization, refers to an open customary for entry delegation, permitting customers to grant web sites or purposes entry to their data on different web sites with out having to provide their passwords. That is completed by making use of an entry token to confirm the consumer’s id and permit the service to entry the useful resource the token is meant for.
When “Sign in with Google” is used to check in to an utility reminiscent of Slack, Google sends the service a set of claims concerning the consumer, together with their e mail handle and the hosted area, which might then be utilized to log customers into their accounts.
This additionally signifies that if a service is solely counting on these items of knowledge to authenticate customers, it additionally opens the door to a situation the place area possession modifications might permit an attacker to regain entry to previous worker accounts.
Truffle additionally identified Google’s OAuth ID token features a distinctive consumer identifier – the sub declare – that would theoretically stop the issue, however that has been discovered to be unreliable. It is price noting that Microsoft’s Entra ID tokens embrace the sub or oid claims to retailer an immutable worth per consumer.
Whereas Google initially responded to the vulnerability disclosure by stating that it’s supposed conduct, it has since re-opened the bug report as of December 19, 2024, awarding Ayrey a bounty of $1,337. It has additionally certified the difficulty as an “abuse-related methodology with high impact.”
Within the meantime, there are not any protections that downstream software program suppliers can take to guard in opposition to the vulnerability in Google’s OAuth implementation. The Hacker Information has reached out to Google for additional remark, and we’ll replace the story if we hear again.
“As an individual, once you’ve been off-boarded from a startup, you lose your ability to protect your data in these accounts, and you are subject to whatever fate befalls the future of the startup and domain,” Ayrey stated. “Without immutable identifiers for users and workspaces, domain ownership changes will continue to compromise accounts.”