Steam Socialite Provider v1 does not correctly validate openid server
Published 29 Jan 2021 · Updated 2 Dec 2024
Is your project on an affected socialiteproviders/steam?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <3.0
- Fixed in
- 3.0
composer require socialiteproviders/steam:^3.0Details
Impact
The outdated version 1 of the Steam Socialite Provider doesn't check properly if the login comes from steamcommunity.com, allowing a malicious actor to substitute their own openID server.
Patches
This vulnerability only affects the outdated v1.x versions of the package. These are no longer maintained, users should upgrade to v3 or v4, which use a hardcoded endpoint to verify the login.
For more information
If you have any questions or comments about this advisory:
- Open an issue in SocialiteProviders/Providers
- Email us at [socialite@atymic.dev](mailto:socialite@atymic.dev)
Is GHSA-hhw9-35p2-q2c5 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected socialiteproviders/steam, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.