# Apache Solr can leak certain passwords due to System Property redaction logic inconsistencies Advisory record · `GHSA-3hwc-rqwp-v36q` - **Identifiers:** `GHSA-3hwc-rqwp-v36q` · `BIT-solr-2023-50291` · `CVE-2023-50291` - **State:** Confirmed - **Severity:** CVSS 7.5 High - **Critical:** No - **Weakness (CWE):** [CWE-522](https://cwe.mitre.org/data/definitions/522.html) - **Tags:** [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md) - **Published:** 9 Feb 2024 - **Updated:** 13 Feb 2025 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 9 Feb 2024, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.apache.solr:solr-core` (Maven): affected `>=6.0.0, <8.11.3 || >=9.0.0, <9.3.0`; fixed in `8.11.3`, `9.3.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Apache Solr solr-core versions 6.0.0 through 8.11.2 and 9.0.0 before 9.3.0 can expose sensitive Java system properties, such as basicauth and aws.secretKey, through the /admin/info/properties endpoint. Only users logged in with the config-read permission can reach this endpoint on Solr Clouds with authorization enabled, and they can then see the exposed credentials on the Admin UI home screen. Upgrade to solr-core 8.11.3 or 9.3.0. Users who cannot upgrade can set the Java system property solr.redaction.system.pattern to a pattern matching password, secret, and basicauth. Written 7 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.033, the 88th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 15:11 UTC: First seen by agentprime - 31 Oct 2026, 15:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3hwc-rqwp-v36q) ## Sources - [GitHub Advisory Database: GHSA-3hwc-rqwp-v36q](https://github.com/advisories/GHSA-3hwc-rqwp-v36q) - [OSV: GHSA-3hwc-rqwp-v36q](https://osv.dev/vulnerability/GHSA-3hwc-rqwp-v36q) - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .