Apache Solr: ConfigSets created during a backup restore command are trusted implicitly (CVE-2024-45217)
Description
Apache Solr versions from 6.6.0 before 8.11.4 and from 9.0.0 before 9.7.0 have a vulnerability where ConfigSets created during a backup restore command are implicitly trusted without proper authentication. This can lead to unauthorized loading of custom code because the 'trusted' flag is set implicitly if missing, which should only happen for authenticated and authorized requests. The issue does not affect Solr instances secured with authentication and authorization. Upgrading to versions 8.11.4 or 9.7.0 mitigates the vulnerability.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2024-45217) in Apache Solr arises from insecure default initialization of ConfigSets created via the Restore command. These ConfigSets copy from backups and are assigned new names but lack explicit 'trusted' metadata. If the 'trusted' flag is missing, Solr treats the ConfigSet as trusted implicitly, allowing it to load custom code into classloaders. This behavior should only occur when the ConfigSet is uploaded through authenticated and authorized requests. Affected versions include Solr >=6.6.0 <8.11.4 and >=9.0.0 <9.7.0. Instances secured with authentication and authorization are not affected. The vulnerability is rated high severity and can be mitigated by upgrading to Solr 8.11.4 or 9.7.0 or by enabling authentication and authorization.
Potential Impact
The vulnerability allows ConfigSets created during backup restore operations to be implicitly trusted without authentication, potentially enabling unauthorized loading of custom code into Solr's classloaders. This could lead to unauthorized code execution or other security risks if the Solr instance is not secured with authentication and authorization.
Mitigation Recommendations
Users are strongly recommended to enable authentication and authorization on Solr instances to prevent exploitation of this vulnerability. Additionally, upgrading affected Solr versions to 8.11.4 or 9.7.0 or later will mitigate the issue. No other specific mitigations are indicated. Instances already secured with authentication and authorization are not vulnerable.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BIT-solr-2024-45217
- Osv Schema Version
- 1.5.0
- Aliases
- CVE-2024-45217
- Ecosystems
- Bitnami
- Database Specific Severity
- High
Threat ID: 6aa005c3acd9273b49ab5bf2
Added to database: 09/08/2026, 12:55:31 UTC
Last enriched: 09/08/2026, 13:17:58 UTC
Last updated: 10/24/2026, 08:45:07 UTC
Views: 48
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.