GHSA-v6xp-ccvx-w52m — ibexa/solr
Fix: ibexa/solr@2f8b711GHSA-v6xp-ccvx-w52m is a security vulnerability in ibexa/solr. A fix is available for ibexa/solr — see the affected versions and patch details below.
Json response for search reveals Solr credentials
Real-World Exposure
ibexa/solrReal-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
An error in Ibexa's Solr search engine results in potential exposure of Solr credentials. This is a critical vulnerability and all supported versions of the engine are affected. Those not using the Solr search engine are not affected.
Patches
The issue is fixed in all supported versions of ibexa/solr, see "Patched versions". An advisory is also published for ezsystems/ezplatform-solr-search-engine, please see that repository. Commit: https://github.com/ibexa/solr/commit/2f8b711874bee1ebe31fb8a6362e0c8e52c53012
Workarounds
None.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | ibexa/solr | ≥ 4.5.0&&< 4.5.4 | 4.5.4composer require ibexa/solr:^4.5.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ibexa/solr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ibexa/solr to 4.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v6xp-ccvx-w52m 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-v6xp-ccvx-w52m can be triaged on real exposure rather than presence alone.
Tailored to GHSA-v6xp-ccvx-w52m. 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-v6xp-ccvx-w52m in your dependencies?
O3 Security finds GHSA-v6xp-ccvx-w52m across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.