GHSA-7crc-r3wg-cfgf
Json response for search reveals Solr credentials
Blast Radius
ezsystems/ezplatform-solr-search-engine🐘ezsystems/ezplatform-solr-search-engine🐘ezsystems/ezplatform-solr-search-engineReal-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 ezsystems/ezplatform-solr-search-engine, see "Patched versions". An advisory is also published for ibexa/solr, please see that repository. Commit: https://github.com/ezsystems/ezplatform-solr-search-engine/commit/1005e02cc32ff15a705857fa56171528a83b9c3e
Workarounds
None.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | ezsystems/ezplatform-solr-search-engine | ≥ 3.3.0&&< 3.3.15 | 3.3.15 |
| 🐘Packagist | ezsystems/ezplatform-solr-search-engine | ≥ 2.0.0&&< 2.0.2 | 2.0.2 |
| 🐘Packagist | ezsystems/ezplatform-solr-search-engine | ≥ 1.7.0&&< 1.7.12 | 1.7.12 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezplatform-solr-search-engine. 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 ezsystems/ezplatform-solr-search-engine to 3.3.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7crc-r3wg-cfgf 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-7crc-r3wg-cfgf 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-7crc-r3wg-cfgf. 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-7crc-r3wg-cfgf in your dependencies?
O3 detects GHSA-7crc-r3wg-cfgf across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.