Skip to content
Sign in
CVE-2024-452178.1HighCWE-1188

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

Apache Software Foundation · Apache Solr

Vendor fix available · Affected: Apache Software Foundation Apache Solr · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.8%probability of exploitation in the next 30 days
55th percentile
050100

Higher than 55% of scored CVEs

8.1HighCVSS 3.1
LowHigh

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • Apache Software Foundation · Apache Solrfrom 6.6.0 before 8.11.4; from 9.0.0 before 9.7.0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Published
October 2024

CoverageNo articles yet

No CyberSIXT article names CVE-2024-45217 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

Updated AboutDevelopersSign in