CVE-2024-56329: 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.
Published Dec 20, 2024 · Updated Dec 26, 2024
Affected packages
joelbutcher/socialstream
- Ecosystem
- Composer (PHP)
- Affected
- >= 6.0.0, < 6.2.0
- Fixed in
- 6.2.0
- Check
composer show joelbutcher/socialstream
joelbutcher/socialstream
- Ecosystem
- Composer (PHP)
- Affected
- < 5.6.0
- Fixed in
- 5.6.0
- Check
composer show joelbutcher/socialstream
Advisory details
From the GitHub Advisory Database (CC BY 4.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.
Credited to carlosmintfan.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
