CVE-2018-8010
Last modified
CVE-2018-8010 is a vulnerability of currently unknown severity. This vulnerability in Apache Solr 6.0.0 to 6.6.3, 7.0.0 to 7.3.0 relates to an XML external entity expansion (XXE) in Solr config files (solrconfig.xml, schema.xml, managed-schema). In addition, Xinclude functionality provided in these config files is also affected in a similar way. EPSS estimates a 3.92% chance of exploitation in the next 30 days.
Description
This vulnerability in Apache Solr 6.0.0 to 6.6.3, 7.0.0 to 7.3.0 relates to an XML external entity expansion (XXE) in Solr config files (solrconfig.xml, schema.xml, managed-schema). In addition, Xinclude functionality provided in these config files is also affected in a similar way. The vulnerability can be used as XXE using file/ftp/http protocols in order to read arbitrary local files from the Solr server or the internal network. Users are advised to upgrade to either Solr 6.6.4 or Solr 7.3.1 releases both of which address the vulnerability. Once upgrade is complete, no other steps are required. Those releases only allow external entities and Xincludes that refer to local files / zookeeper resources below the Solr instance directory (using Solr's ResourceLoader); usage of absolute URLs is denied. Keep in mind, that external entities and XInclude are explicitly supported to better structure config files in large installations. Before Solr 6 this was no problem, as config files were not accessible through the APIs.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Solr | >= 6.0.0, <= 6.6.3 |
| Apache | Solr | >= 7.0.0, <= 7.3.0 |
References
- http://www.securityfocus.com/bid/104239Third Party Advisory, VDB Entry
- https://mail-archives.apache.org/mod_mbox/www-announce/201805.mbox/%3C08a801d3f0f9%24df46d300%249dd47900%24%40apache.org%3EMailing List, Mitigation, Vendor Advisory
- http://www.securityfocus.com/bid/104239Third Party Advisory, VDB Entry
- https://mail-archives.apache.org/mod_mbox/www-announce/201805.mbox/%3C08a801d3f0f9%24df46d300%249dd47900%24%40apache.org%3EMailing List, Mitigation, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-8010?
How severe is CVE-2018-8010?
How do I fix CVE-2018-8010?
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 2018
- CVE-2018-8004There are multiple HTTP smuggling and cache poisoning issues…
- CVE-2018-8005When there are multiple ranges in a range request, Apache Tr…
- CVE-2018-8006An instance of a cross-site scripting vulnerability was iden…6.1
- CVE-2018-8007Apache CouchDB administrative users can configure the databa…
- CVE-2018-8008Apache Storm version 1.0.6 and earlier, 1.2.1 and earlier, a…
- CVE-2018-8009Apache Hadoop 3.1.0, 3.0.0-alpha to 3.0.2, 2.9.0 to 2.9.1, 2…
- CVE-2018-8011By specially crafting HTTP requests, the mod_md challenge ha…
- CVE-2018-8012No authentication/authorization is enforced when a server at…7.5
- CVE-2018-8013In Apache Batik 1.x before 1.10, when deserializing subclass…
- CVE-2018-8014The defaults settings for the CORS filter provided in Apache…
- CVE-2018-8015In Apache ORC 1.0.0 to 1.4.3 a malformed ORC file can trigge…
- CVE-2018-8016The default configuration in Apache Cassandra 3.8 through 3.…
Are you affected by CVE-2018-8010?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
