What is CVE-2023-50386?A high-severity flaw in Solr, explained.
CVE-2023-50386 is a high-severity flaw (CVSS 8.8) in Solr from Apache, published on 9 February 2024. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 84%. If you run an affected version, plan in the vendor’s fix.
Published 9 February 2024. Record last updated 17 June 2026. We keep this page's data up to date.
What is CVE-2023-50386? In plain terms.
It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
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.
What kind of flaw is it?
- CWE-434Unrestricted Upload of File with Dangerous Type
- CWE-913Improper Control of Dynamically-Managed Code Resources
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstAn ordinary user account
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is CVE-2023-50386 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 84%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2023-50386 scores 76. Action: Patch now.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2023-50386 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2023-50386? One product.
The published record lists 1 product from 1 vendor. Versions are shown as published: "6.0.0 to before 8.11.3" means from 6.0.0 up to, but not including, 8.11.3. If you run one of these, check your version, then go to the fix below.
How do I fix CVE-2023-50386? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the latest update from the vendor. The references list where the vendor has published details.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2023-50386 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Improper Control of Dynamically-Managed Code Resources, Unrestricted Upload of File with Dangerous Type, Inclusion of Functionality from Untrusted Control Sp...
- Matched to
- Solr on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2023-50386 is a high-severity flaw in Solr from Apache, published on 9 February 2024. It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It scores 8.8 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2023-50386 is 76 out of 100, which is High. Its action is "Patch now". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 84%. That can change at any time, which is why we keep watching.
For Solr from Apache: 6.0.0 to before 8.11.3, 9.0.0 to before 9.4.1.
Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.