NVD / CVE Program· CNA apache

CVE-2024-45217: Apache Solr: ConfigSets created during a backup restore command are trusted implicitly

Noroxi assessment

Priority: Monitor (action score 32/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.74% (FIRST EPSS); higher than 54.5% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Apache Software Foundation Apache Solr 8.11.4, 9.7.0.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Apache Software Foundation Apache Solr 8.11.4, 9.7.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Insecure Default Initialization of Resource vulnerability in Apache Solr. 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. ConfigSets 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. "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. This 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. Users 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.

HighCVSS 8.1 · v3.1—No exploit Fix available

GHSA-h7w9-c5vx-x7j3

Published: Oct 16, 2024
Updated: Jun 17, 2026
EPSS: 0.7% · 54th percentile
CWE: CWE-1188

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 32 / 40 · 8.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.7%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
apache	solr	cpe:2.3:a:apache:solr

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

apache solr6.6.0 and later · before 8.11.4
apache solr9.0.0 and later · before 9.7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

Apache Software Foundation Apache Solr
- 6.6.0 and later · before 8.11.4affected · semver
- 9.0.0 and later · before 9.7.0affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Maven	org.apache.solr:solr	from 6.6.0 · before 8.11.4	8.11.4
Maven	org.apache.solr:solr	from 9.0.0 · before 9.7.0	9.7.0

Same product

apache: all records

Other highest-scoring records for the same primary product.

CVE-2019-17558Apache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter.KEV
90Now
CVE-2019-0193In Apache Solr, the DataImportHandler, an optional but popular module to pull in data from databases and other sources, has a feature in whiKEV
83Now
CVE-2024-45216Apache Solr: Authentication bypass possible using a fake URL Path ending
67This week

Published before and after this one in the same product

← EarlierCVE-2023-50298Feb 9, 2024 · Apache Solr: Solr can expose ZooKeeper credentials via Streaming Expressions
30Monitor
← EarlierCVE-2023-50386Feb 9, 2024 · Apache Solr: Backup/Restore APIs allow for deployment of executables in malicious ConfigSets
60This week
Later →CVE-2024-52012Jan 27, 2025 · Apache Solr: Configset upload on Windows allows arbitrary path write-access
33Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Apache Software Foundation Apache Solr	8.11.4	Vendor (CNA)
Apache Software Foundation Apache Solr	9.7.0	Vendor (CNA)
Maven:org.apache.solr:solr	8.11.4	Package registry (OSV)
Maven:org.apache.solr:solr	9.7.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Liu Huajinreporter

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).