CVE-2024-45217
Last modified
CVE-2024-45217 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. 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. EPSS estimates a 0.72% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Solr | >= 6.6.0, < 8.11.4 |
| Apache | Solr | >= 9.0.0, < 9.7.0 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-45217?
How severe is CVE-2024-45217?
How do I fix CVE-2024-45217?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-45205An Improper Certificate Validation on the UniFi iOS App mana…7.1
- CVE-2024-45206A vulnerability in Veeam Service Provider Console has been i…6.5
- CVE-2024-45207DLL injection in Veeam Agent for Windows can occur if the sy…7
- CVE-2024-45208The Versa Director SD-WAN orchestration platform which makes…9.8
- CVE-2024-4521A vulnerability classified as problematic has been found in …6.1
- CVE-2024-45216Improper Authentication vulnerability in Apache Solr. Solr …9.8
- CVE-2024-45219Account users in Apache CloudStack by default are allowed to…8.5
- CVE-2024-4522A vulnerability classified as problematic was found in Campc…6.1
- CVE-2024-45229The Versa Director offers REST APIs for orchestration and ma…6.6
- CVE-2024-4523A vulnerability, which was classified as problematic, has be…6.1
- CVE-2024-45230An issue was discovered in Django 5.1 before 5.1.1, 5.0 befo…7.5
- CVE-2024-45231An issue was discovered in Django v5.1.1, v5.0.9, and v4.2.1…5.3
Are you affected by CVE-2024-45217?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
