How severe is GHSA-hhw9-35p2-q2c5?

No CVSS score has been assigned to GHSA-hhw9-35p2-q2c5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hhw9-35p2-q2c5?

GHSA-hhw9-35p2-q2c5 affects the following packages: socialiteproviders/steam (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-hhw9-35p2-q2c5?

Update socialiteproviders/steam to 3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hhw9-35p2-q2c5 is resolved across your whole dependency graph.

How do I detect GHSA-hhw9-35p2-q2c5 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for socialiteproviders/steam. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hhw9-35p2-q2c5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-hhw9-35p2-q2c5?

O3 pinpoints whether GHSA-hhw9-35p2-q2c5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-hhw9-35p2-q2c5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-hhw9-35p2-q2c5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-hhw9-35p2-q2c5 published, and has it been updated?

GHSA-hhw9-35p2-q2c5 was published on January 29, 2021 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-hhw9-35p2-q2c5

GHSA-hhw9-35p2-q2c5 is a security vulnerability in socialiteproviders/steam. O3 Security confirms whether GHSA-hhw9-35p2-q2c5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Steam Socialite Provider v1 does not correctly validate openid server

Published

Jan 29, 2021

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘socialiteproviders/steam

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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 [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`socialiteproviders/steam`	all versions	3.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for socialiteproviders/steam. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update socialiteproviders/steam to 3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hhw9-35p2-q2c5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-hhw9-35p2-q2c5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hhw9-35p2-q2c5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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](https://github.com/SocialiteProviders/Providers) * Email u

O3 Security · Impact-Aware SCA

Is GHSA-hhw9-35p2-q2c5 in your dependencies?

O3 detects GHSA-hhw9-35p2-q2c5 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works