Remote code execution via implicitly trusted ConfigSets
Published Oct 16, 2024 · Updated Oct 16, 2024
Insecure resource initialization in Apache Solr 6.6.0 before 8.11.4 and 9.0.0 before 9.7.0 allows remote attackers to execute code. The backup Restore path creates a renamed ConfigSet without trusted metadata, and Solr treats missing metadata as trusted before allowing custom code into classloaders. Exploitation requires an instance without authentication and authorization and a crafted ConfigSet, granting code execution in the Solr process.
Summary
What happened
Insecure resource initialization in Apache Solr 6.6.0 before 8.11.4 and 9.0.0 before 9.7.0 allows remote attackers to execute code. The backup Restore path creates a renamed ConfigSet without trusted metadata, and Solr treats missing metadata as trusted before allowing custom code into classloaders. Exploitation requires an instance without authentication and authorization and a crafted ConfigSet, granting code execution in the Solr process.
The record
- CVE
- CVE-2024-45217
- Published
- Oct 16, 2024
- Updated
- Oct 16, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Solr
- Classifications
- CWE-1188, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2024CVE publishedPublication date reported by the CVE source.
- Oct 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.6.0 <8.11.4
- Affected versionversion=9.0.0 <9.7.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- SOLR-17418 reproduction sequenceproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo