dbcve.org
SolrApplication · Apache

CVE-2024-45217

HIGH · 8.1 CVSS v3.1 Published 2024-10-16
Fix available
A fix is available. Upgrade to 8.11.4 / 9.7.0 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Solr ConfigSets created via Restore command are missing the 'trusted' metadata flag. Since ConfigSets without this flag are implicitly trusted when metadata is absent, this allows untrusted ConfigSets to become trusted without authentication, enabling them to load arbitrary code into classloaders.

MitigationEnable Authentication and Authorization for Solr instances, or upgrade to Solr 9.7.0/8.11.4 which contain the fix for proper trusted flag initialization.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SolrApplication
Affected:>= 6.6.0, < 8.11.4>= 9.0.0, < 9.7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Solr version
    Run 'bin/solr -v' from the Solr installation directory, or check the solr-version file in the distribution, or query the Solr admin API at /solr/admin/info/system
    Affected if The version is >= 6.6.0 and < 8.11.4, OR >= 9.0.0 and < 9.7.0
  2. List existing ConfigSets
    Query the Solr admin API at /solr/admin/configs?action=LIST, or list contents of the configsets directory (typically ${solr.home}/configsets/)
    Affected if Any ConfigSets exist in the environment
  3. Inspect ConfigSet trusted metadata
    For each ConfigSet, check the configset.properties file located in the ConfigSet's directory (e.g., configsets/<name>/configset.properties). Look for the 'trusted' property. If the property is absent or set to 'true', the ConfigSet is treated as trusted.
    Affected if Any ConfigSet is missing the 'trusted' property entirely, or has 'trusted=true' without explicit justification (this is the vulnerable state for ConfigSets created via Restore in affected versions)
  4. Identify ConfigSets created via Restore
    Review audit logs or history for ConfigSet creation events with 'restore' in the operation type, or check if any ConfigSets with missing trusted metadata correspond to restore operations you have performed
    Affected if Any ConfigSets were created using the Restore command and are missing the explicit 'trusted=false' flag in their metadata

You are affected if your Solr version is in the vulnerable range AND you have ConfigSets (particularly those created via Restore) that lack an explicit 'trusted=false' flag in their configset.properties, as these are implicitly treated as trusted.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.11.4 / 9.7.0 or later
Fixed in 8.11.49.7.0
Interim mitigation

Enable Authentication and Authorization for Solr instances, or upgrade to Solr 9.7.0/8.11.4 which contain the fix for proper trusted flag initialization.

Recommended fix High confidence

8.11.4 for 8.x branches, 9.7.0 for 9.x branches

  1. 1. Identify current Apache Solr version by checking the solr -version command or the version file in the Solr installation directory
  2. 2. Determine upgrade path: if running 8.x, upgrade to 8.11.4; if running 9.x, upgrade to 9.7.0
  3. 3. Create a complete backup of the Solr data directory (by default, solr.data.dir or server/solr)
  4. 4. Back up all custom ConfigSets, Solr conf files, and any custom plugins or libraries
  5. 5. Review the Solr upgrade guide for your version path at solr.apache.org/guide to check for any intermediate upgrade steps required
  6. 6. Test the upgrade in a non-production environment first
  7. 7. Stop the Solr service before upgrading
  8. 8. Install the fixed version (8.11.4 or 9.7.0) using your installation method (tar, docker, package manager, or solr-installer)
Caveat Review Solr 8.x and 9.x release notes for breaking changes; major version upgrades may require configuration or API adjustments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Solr Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45217 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45217 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data