SolrApplication · Apache
CVE-2023-50298
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Solr.This issue affects Apache Solr: from 6.0.0 through 8.11.2, from 9.0.0 before 9.4.1. Solr Streaming Expressions allows users to extract data from other Solr Clouds, using a "zkHost" parameter. When original SolrCloud is setup to use ZooKeeper credentials and ACLs, they will be sent to whatever "zkHost" the user provides. An attacker could setup a server to mock ZooKeeper, that accepts ZooKeeper requests with credentials and ACLs and extracts the sensitive information, then send a streaming expression using the mock server's address in "zkHost". Streaming Expressions are exposed via the "/streaming" handler, with "read" permissions. Users are recommended to upgrade to version 8.11.3 or 9.4.1, which fix the issue. From these versions on, only zkHost values that have the same server address (regardless of chroot), will use the given ZooKeeper credentials and ACLs when connecting.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Solr Streaming Expressions with zkHost parameter inadvertently sends ZooKeeper credentials and ACLs to arbitrary server addresses, allowing attackers to set up mock ZooKeeper servers to capture these credentials. The vulnerability is exploitable through the /streaming handler which requires only read permissions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
SolrApplication
>= 6.0.0, < 8.11.3>= 9.0.0, < 9.4.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Solr versionRun 'solr -v' or check the Solr admin UI version display, or look for the version in solr-*.jar filenames in the installation directoryAffected if The installed version is >= 6.0.0 and < 8.11.3, OR >= 9.0.0 and < 9.4.1
-
Verify /streaming handler is accessibleCheck if the /streaming request handler is enabled in solrconfig.xml. Look for a <requestHandler name='/streaming' ...> entry in the configurationAffected if The /streaming handler is enabled and publicly or semi-publicly accessible on the network
-
Confirm ZooKeeper credentials or ACLs are configuredExamine the Solr configuration for zkCredentials or zkACLs settings, typically found in solr.xml or in the zkHost parameter within streaming expressionsAffected if ZooKeeper credentials or ACLs are configured and could be transmitted via the zkHost parameter
-
Check for zkHost usage in streaming expressionsReview any streaming expression definitions or historical queries that use the zkHost parameter, particularly those that may point to external or uncontrolled ZooKeeper addressesAffected if zkHost parameter is used with addresses outside your trusted ZooKeeper infrastructure
You are affected if you run a vulnerable Solr version (6.x through 8.11.2 or 9.x through 9.4.0), have the /streaming handler accessible, and use ZooKeeper credentials/ACLs with potentially untrusted zkHost addresses
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped8.11.39.4.1
Upgrade to Apache Solr 8.11.3 or 9.4.1, which restricts ZooKeeper credential/ACL usage to zkHost values with matching server addresses. Until upgraded, restrict access to the /streaming handler.
8.11.3 for 8.x users; 9.4.1 for 9.x users
- 1. Identify the current Apache Solr version in use by checking the Solr admin UI or the solr version file
- 2. If running version 6.x, plan migration to version 8.11.3 (or later 8.x) as Solr 6.x is end-of-life
- 3. If running version 8.0.0 through 8.11.2, upgrade to version 8.11.3
- 4. If running version 9.0.0 through 9.4.0, upgrade to version 9.4.1
- 5. Download the appropriate Solr release from the official Apache Solr downloads page (solr.apache.org/downloads.html)
- 6. Test the upgrade in a non-production environment first
- 7. Back up all Solr data, configurations, and ZooKeeper znodes before upgrading
- 8. Stop the Solr service
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Solr
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50298 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-50298 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data