GHSA-5629-8855-gf4g
CRITICALGHSA-5629-8855-gf4g is a critical-severity (CVSS 9.3) vulnerability in solidus_core. O3 Security confirms whether GHSA-5629-8855-gf4g is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Authentication Bypass by CSRF Weakness
Real-World Exposure
solidus_core💎solidus_core💎solidus_coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The actual vulnerability has been discovered on solidus_auth_devise. See GHSA-xm34-v85h-9pg2 for details.
The security advisory here exists to provide an extra layer of security in the form of a monkey patch for users who don't update solidus_auth_devise. For this reason, it has been marked as low impact on this end.
Patches
For extra security, update solidus_core to versions 3.1.3, 3.0.3 or 2.11.12.
Workarounds
Look at the workarounds described at GHSA-xm34-v85h-9pg2.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in solidus_auth_devise or a discussion in solidus
- Email us at [email protected]
- Contact the core team on Slack
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | solidus_core | all versions | 2.11.12 |
| 💎RubyGems | solidus_core | ≥ 3.0.0&&< 3.0.3 | 3.0.3 |
| 💎RubyGems | solidus_core | ≥ 3.1.0&&< 3.1.3 | 3.1.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for solidus_core. 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 solidus_core to 2.11.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5629-8855-gf4g 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-5629-8855-gf4g 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-5629-8855-gf4g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-5629-8855-gf4g in your dependencies?
O3 detects GHSA-5629-8855-gf4g across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.