Headline
GHSA-3q97-vjpp-c8rp: Socialstream has a Potential Account Takeover Vulnerability in Social Account Linking Due to Missing User Consent After OAuth Callback
Description
When linking a social account to an already authenticated user, the lack of a confirmation step introduces a security risk. This is exacerbated if ->stateless() is used in the Socialite configuration, bypassing state verification and making the exploit easier. Developers should ensure that users explicitly confirm account linking and avoid configurations that skip critical security checks.
Resolution
Socialstream v6.2 introduces a new custom route that requires a user to “Confirm” or “Deny” a request to link a social account.
- GitHub Advisory Database
- GitHub Reviewed
- GHSA-3q97-vjpp-c8rp
Socialstream has a Potential Account Takeover Vulnerability in Social Account Linking Due to Missing User Consent After OAuth Callback
High severity GitHub Reviewed Published Dec 20, 2024 in joelbutcher/socialstream • Updated Dec 20, 2024
Package
composer joelbutcher/socialstream (Composer)
Affected versions
< 6.2.0
Description
When linking a social account to an already authenticated user, the lack of a confirmation step introduces a security risk. This is exacerbated if ->stateless() is used in the Socialite configuration, bypassing state verification and making the exploit easier. Developers should ensure that users explicitly confirm account linking and avoid configurations that skip critical security checks.
Resolution
Socialstream v6.2 introduces a new custom route that requires a user to “Confirm” or “Deny” a request to link a social account.
References
- GHSA-3q97-vjpp-c8rp
- joelbutcher/socialstream@ae4dc39
Published to the GitHub Advisory Database
Dec 20, 2024
Last updated
Dec 20, 2024