CVE-2023-50292 json
Apache Solr: Solr Schema Designer blindly "trusts" all configsets, possibly leading to RCE by unauthenticated users
published 2024-02-09 2 y ago modified 2026-09-08 2 mo ago also BIT-solr-2023-50292 , EUVD-2024-0513 , GHSA-4wxw-42wx-2wfx
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.0%
- EPSS 3.0% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
Incorrect Permission Assignment for Critical Resource, Improper Control of Dynamically-Managed Code Resources vulnerability in Apache Solr.
This issue affects Apache Solr: from 8.10.0 through 8.11.2, from 9.0.0 before 9.3.0.
The Schema Designer was introduced to allow users to more easily configure and test new Schemas and configSets. However, when the feature was created, the "trust" (authentication) of these configSets was not considered. External library loading is only available to configSets that are "trusted" (created by authenticated users), thus non-authenticated users are unable to perform Remote Code Execution. Since the Schema Designer loaded configSets without taking their "trust" into account, configSets that were created by unauthenticated users were allowed to load external libraries when used in the Schema Designer.
Users are recommended to upgrade to version 9.3.0, which fixes the issue.
Patch / fix
- maven org.apache.solr:solr-core 8.11.3, 9.3.0
- bitnami solr 8.11.3, 9.4.1
- Apache Software Foundation Apache Solr 9.3.0
- lucene-solr Debian 14, Debian 13, Debian 12 3.6.2+dfsg-23
debian advisories DEBIAN-CVE-2023-50292
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-50292 updated cvss 6.3
Solr: Schema Designer trusts all configsets, possibly leading to RCE by unauthenticated users
-
Red Hat Fuse 7 solr solraffected: no fix planned “Will not fix”
-
Red Hat JBoss Enterprise Application Platform 6 solr solraffected: no fix planned “Out of support scope”
-
Red Hat Data Grid 8 solr solr Red Hat Integration Camel K 1 camel-solr camel-solr Red Hat JBoss Enterprise Application Platform 8 solr solrnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
3.02% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.solr:solr-core | >=9.0.0, <9.3.0 >=8.10.0, <8.11.3 |
9.3.0 8.11.3 |
| bitnami | solr | >=6.0.0, <8.11.3 >=9.0.0, <9.4.1 |
8.11.3 9.4.1 |
Affected products
- Apache Software Foundation Apache Solr
Classification
- Weakness
-
- CWE-732 Incorrect Permission Assignment for Critical Resource
References
-
github.com
/apache/lucene-solr/commit/6e9ed203b30958396bdfd41760d426b386646865
web
-
github.com
/apache/solr/commit/d07751cfaa8065bea8bd43f59e758e50d50c2419
web
-
solr.apache.org
/security.html#cve-2023-50298-apache-solr-can-expose-zookeeper-credentials-via-streaming-expressions
vendor-advisory, web, advisory
-
openwall.com
/lists/oss-security/2024/02/09/3
web, mailing-list, discussion
-
nvd.nist.gov
/vuln/detail/CVE-2023-50292
advisory, web
-
issues.apache.org
/jira/browse/SOLR-16777
web
Sources
- CVE List CVE-2023-50292
- GitHub Advisory GHSA-4wxw-42wx-2wfx
- NVD CVE-2023-50292
- OSV BIT-solr-2023-50292
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.