CVE-2024-45217: Solr Remote Code Execution Vulnerability
HIGHCVE-2024-45217 is a HIGH (CVSS 8.1) remote code execution vulnerability (CWE-1188: Initialization of a Resource with an Insecure Default) affecting Solr libraries in the Maven ecosystem. The issue involves insecure default initialization of resource vulnerability in apache solr. Remediation is available by upgrading affected packages to version 8.11.4, 9.7.0.
CVE-2024-45217 at a Glance
Security Impact
CVSS: 8.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).
How to Fix CVE-2024-45217
To remediate this vulnerability, upgrade all affected Solr dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.apache.solr</groupId>
<artifactId>solr</artifactId>
<version>8.11.4</version>
</dependency><dependency>
<groupId>org.apache.solr</groupId>
<artifactId>solr</artifactId>
<version>9.7.0</version>
</dependency>Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.apache.solrHow to Check if You Are Affected
To determine whether your Java application is affected by CVE-2024-45217, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.apache.solrAnalyze the terminal output to locate any version of Solr in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 8.11.4), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.apache.solr command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-1188: Initialization of a Resource with an Insecure Default, where the product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure. In Solr, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2024-45217 Affected Solr Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.apache.solr:solr
|
Maven |
≥ 6.6.0
< 8.11.4
|
8.11.4
|
|
org.apache.solr:solr
|
Maven |
≥ 9.0.0
< 9.7.0
|
9.7.0
|
References
Frequently Asked Questions
What is CVE-2024-45217?
Which Solr versions are affected?
What version fixes CVE-2024-45217?
Is solr affected?
What is the CVSS score of CVE-2024-45217?
What CWE is associated with CVE-2024-45217?
How can I check Maven dependencies for CVE-2024-45217?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-h7w9-c5vx-x7j3",
"modified" : "2025-07-02T14:20:10Z",
"published" : "2024-10-16T09:30:31Z",
"aliases" : [ "CVE-2024-45217" ],
"summary" : "Insecure Default Initialization of Resource vulnerability in Apache Solr",
"details" : "New ConfigSets that are created via a Restore command, which copy a configSet from the backup and give it a new name, are created without setting the \"trusted\" metadata.\nConfigSets that do not contain the flag are trusted implicitly if the metadata is missing, therefore this leads to \"trusted\" ConfigSets that may not have been created with an Authenticated request.\n\"trusted\" ConfigSets are able to load custom code into classloaders, therefore the flag is supposed to only be set when the request that uploads the ConfigSet is Authenticated & Authorized.\n\nThis issue affects Apache Solr: from 6.6.0 before 8.11.4, from 9.0.0 before 9.7.0. This issue does not affect Solr instances that are secured via Authentication/Authorization.\n\nUsers are primarily recommended to use Authentication and Authorization when running Solr. However, upgrading to version 9.7.0, or 8.11.4 will mitigate this issue otherwise.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.apache.solr:solr"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "6.6.0"
}, {
"fixed" : "8.11.4"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.apache.solr:solr"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "9.0.0"
}, {
"fixed" : "9.7.0"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-45217"
}, {
"type" : "WEB",
"url" : "https://issues.apache.org/jira/browse/SOLR-17418"
}, {
"type" : "WEB",
"url" : "https://solr.apache.org/security.html#cve-2024-45217-apache-solr-configsets-created-during-a-backup-restore-command-are-trusted-implicitly"
}, {
"type" : "PACKAGE",
"url" : "http://svn.apache.org/viewvc/lucene/dev/branches/branch_4x/solr/webapp"
}, {
"type" : "WEB",
"url" : "http://www.openwall.com/lists/oss-security/2024/10/15/9"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-1188" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2024-10-16T17:54:12Z",
"nvd_published_at" : "2024-10-16T08:15:05Z"
}
}