What is CVE-2023-50298?

CVE-2023-50298 is a medium-severity security vulnerability in org.apache.solr:solr-solrj-streaming (maven), affecting versions >= 9.0.0, < 9.4.1. It is fixed in 9.4.1, 8.11.3.

How severe is CVE-2023-50298?

CVE-2023-50298 has a CVSS score of 7.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2023-50298?

org.apache.solr:solr-solrj-streaming (maven) versions >= 9.0.0, = 9.0.0, < 9.4.1.

Is there a fix for CVE-2023-50298?

Yes. CVE-2023-50298 is fixed in 9.4.1, 8.11.3. Upgrade to this version or later.

Is CVE-2023-50298 exploitable, and should I be worried?

Whether CVE-2023-50298 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-50298 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2023-50298

Q: How severe is CVE-2023-50298?

CVE-2023-50298 has a CVSS score of 7.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2023-50298?

org.apache.solr:solr-solrj-streaming (maven) versions >= 9.0.0, = 9.0.0, < 9.4.1.

Q: Is there a fix for CVE-2023-50298?

Yes. CVE-2023-50298 is fixed in 9.4.1, 8.11.3. Upgrade to this version or later.

Q: Is CVE-2023-50298 exploitable, and should I be worried?

Whether CVE-2023-50298 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-50298 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2023-50298?

Upgrade: org.apache.solr:solr-solrj-streaming to 9.4.1 or later, org.apache.solr:solr-solrj-streaming to 8.11.3 or later, org.apache.solr:solr-solrj to 9.4.1 or later, org.apache.solr:solr-solrj to 8.11.3 or later.

Summary

Apache Solr's Streaming Expressions allow users to extract data from other Solr Clouds

Exposure 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.

Impact

CVE-2023-50298 has a CVSS score of 7.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.4.1, 8.11.3); upgrading removes the vulnerable code path.

Affected versions

org.apache.solr:solr-solrj-streaming (>= 9.0.0, < 9.4.1) org.apache.solr:solr-solrj-streaming (>= 6.0.0, < 8.11.3) org.apache.solr:solr-solrj (>= 9.0.0, < 9.4.1) org.apache.solr:solr-solrj (>= 6.0.0, < 8.11.3)

Security releases

org.apache.solr:solr-solrj-streaming → 9.4.1 (maven) org.apache.solr:solr-solrj-streaming → 8.11.3 (maven) org.apache.solr:solr-solrj → 9.4.1 (maven) org.apache.solr:solr-solrj → 8.11.3 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.solr:solr-solrj-streaming to 9.4.1 or later; org.apache.solr:solr-solrj-streaming to 8.11.3 or later; org.apache.solr:solr-solrj to 9.4.1 or later; org.apache.solr:solr-solrj to 8.11.3 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2023-50298? CVE-2023-50298 is a medium-severity security vulnerability in org.apache.solr:solr-solrj-streaming (maven), affecting versions >= 9.0.0, < 9.4.1. It is fixed in 9.4.1, 8.11.3.
How severe is CVE-2023-50298? CVE-2023-50298 has a CVSS score of 7.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2023-50298?
- org.apache.solr:solr-solrj-streaming (maven) (versions >= 9.0.0, < 9.4.1)
- org.apache.solr:solr-solrj (maven) (versions >= 9.0.0, < 9.4.1)
Is there a fix for CVE-2023-50298? Yes. CVE-2023-50298 is fixed in 9.4.1, 8.11.3. Upgrade to this version or later.
Is CVE-2023-50298 exploitable, and should I be worried? Whether CVE-2023-50298 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-50298 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-50298?
- Upgrade org.apache.solr:solr-solrj-streaming to 9.4.1 or later
- Upgrade org.apache.solr:solr-solrj-streaming to 8.11.3 or later
- Upgrade org.apache.solr:solr-solrj to 9.4.1 or later
- Upgrade org.apache.solr:solr-solrj to 8.11.3 or later