CriticalGHSA-v6xp-ccvx-w52m

Json response for search reveals Solr credentials

Published 3 Nov 2023 · Updated 4 Dec 2024

Is your project on an affected ibexa/solr?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

ibexa/solrComposer
Affected
>=4.5.0 <4.5.4
Fixed in
4.5.4
Update to the fixed version for your release line, for example:composer require ibexa/solr:^4.5.4

Details

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

https://developers.ibexa.co/security-advisories/ibexa-sa-2023-005-vulnerabilities-in-solr-search-and-file-downloads

Is GHSA-v6xp-ccvx-w52m 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 ibexa/solr, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.