Solr vulnerabilitiesAnd the versions its exploited flaws hit.
Solr is made by Apache. We track 40 published vulnerabilities in it, across 131 versions. 3 of them are on the list of flaws known to be exploited, the newest added on 10 October 2023. If you run Solr, check your version against the exploited flaws below and patch those first.
The most recent Solr flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023. We keep watching the known-exploited list.
Which versions of Solr do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "before 9.4.0" means every version up to, but not including, 9.4.0. Find your version, then patch.
- CVE-2023-44487Exploited list, 10 Oct 2023
HTTP/2 Rapid Reset Attack Vulnerability
before 9.4.0 - CVE-2019-0193Exploited list, 10 Dec 2021
Apache Solr DataImportHandler Code Injection Vulnerability
before 7.7.38.1.0 to before 8.1.2 - CVE-2019-17558Exploited list, 3 Nov 2021
Apache Solr VelocityResponseWriter Plug-In Remote Code Execution Vulnerability
5.0.0 to before 7.7.38.0.0 to before 8.4.0
Which Solr vulnerabilities are being exploited?
3 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 7.5HTTP/2 Rapid Reset Attack Vulnerability
HTTP/2 contains a rapid reset vulnerability that allows for a distributed denial-of-service attack (DDoS).
- 7.2Apache Solr DataImportHandler Code Injection Vulnerability
The optional Apache Solr module DataImportHandler contains a code injection vulnerability.
- 7.5Apache Solr VelocityResponseWriter Plug-In Remote Code Execution Vulnerability
The Apache Solr VelocityResponseWriter plug-in contains an unspecified vulnerability which can allow for remote code execution.
Which Solr flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
- 99%
Apache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter.
- 93%CVE-2021-27905Critical
The ReplicationHandler (normally registered at "/replication" under a Solr core) in Apache Solr has a "masterUrl" (also "leaderUrl" alias) parameter that is used to designate another ReplicationHandler on another...
- 92%CVE-2017-12629Critical
Remote code execution occurs in Apache Solr before 7.1 with Apache Lucene before 7.1 by exploiting XXE in conjunction with use of a Config API add-listener command to reach the RunExecutableListener class.
- 84%CVE-2023-50386High
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...
- 84%
In Apache Solr, the DataImportHandler, an optional but popular module to pull in data from databases and other sources, has a feature in which the whole DIH configuration can come from a request's "dataConfig" parameter.
- 79%CVE-2020-13957Critical
Apache Solr versions 6.6.0 to 6.6.6, 7.0.0 to 7.7.3 and 8.0.0 to 8.6.2 prevents some features considered dangerous (which could be used for remote code execution) to be configured in a ConfigSet that's uploaded via...
- 78%CVE-2019-0192Critical
In Apache Solr versions 5.0.0 to 5.5.5 and 6.0.0 to 6.6.5, the Config API allows to configure the JMX server via an HTTP POST request.
- 78%CVE-2020-27223Medium
In Eclipse Jetty 9.4.6.v20170531 to 9.4.36.v20210114 (inclusive), 10.0.0, and 11.0.0 when Jetty handles a request containing multiple Accept headers with a large number of “quality” (i.e.
- 68%CVE-2023-50290Medium
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Solr.
Running Solr? 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 flaw being exploited affects software Acme tracks
HTTP/2 contains a rapid reset vulnerability that allows for a distributed denial-of-service attack (DDoS).
- Matched to
- Solr on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 40 published vulnerabilities listed under the name Solr, across 131 versions. The most recent Solr flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023.
3 are on the list of flaws known to be exploited. The most recently added are CVE-2023-44487, CVE-2019-0193 and CVE-2019-17558.
Each flaw names its own versions, usually as ranges. The newest, CVE-2023-44487, affects before 9.4.0. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Solr. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.