CVE-2023-50386

Improper Control of Dynamically-Managed Code Resources, Unrestricted Upload of File with Dangerous Type, Inclusion of Functionality from Untrusted Control Sphere 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.

In the affected versions, Solr ConfigSets accepted Java jar and class files to be uploaded through the ConfigSets API.
When backing up Solr Collections, these configSet files would be saved to disk when using the LocalFileSystemRepository (the default for backups).
If the backup was saved to a directory that Solr uses in its ClassPath/ClassLoaders, then the jar and class files would be available to use with any ConfigSet, trusted or untrusted.

When Solr is run in a secure way (Authorization enabled), as is strongly suggested, this vulnerability is limited to extending the Backup permissions with the ability to add libraries.
Users are recommended to upgrade to version 8.11.3 or 9.4.1, which fix the issue.
In these versions, the following protections have been added:

• Users are no longer able to upload files to a configSet that could be executed via a Java ClassLoader.
• The Backup API restricts saving backups to directories that are used in the ClassLoader.

The application accepts file uploads without adequately restricting the file type or content. Typical impact: remote code execution if the uploaded file can be served and executed on the server.

CVE-2023-50386 has a CVSS score of 8.8 (High). The vector is network-reachable, low 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 (8.11.3, 9.4.1); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2023-50386? CVE-2023-50386 is a high-severity unrestricted upload of dangerous file types vulnerability in org.apache.solr:solr-core (maven), affecting versions >= 6.0.0, < 8.11.3. It is fixed in 8.11.3, 9.4.1. The application accepts file uploads without adequately restricting the file type or content.
2. How severe is CVE-2023-50386? CVE-2023-50386 has a CVSS score of 8.8 (High). 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.
3. Which versions of org.apache.solr:solr-core are affected by CVE-2023-50386? org.apache.solr:solr-core (maven) versions >= 6.0.0, < 8.11.3 is affected.
4. Is there a fix for CVE-2023-50386? Yes. CVE-2023-50386 is fixed in 8.11.3, 9.4.1. Upgrade to this version or later.
5. Is CVE-2023-50386 exploitable, and should I be worried? Whether CVE-2023-50386 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
6. What actually determines whether CVE-2023-50386 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.
7. How do I fix CVE-2023-50386?
   • Upgrade org.apache.solr:solr-core to 8.11.3 or later
   • Upgrade org.apache.solr:solr-core to 9.4.1 or later