CVE-2017-12629 is a critical-severity (CVSS 9.8) XML External Entity (XXE) vulnerability in org.apache.solr:solr-core. 4 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.solr:solr-core — see the affected versions and patch details below.
Remote code execution occurs in Apache Solr
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2017-12629 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 394,415 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.apache.solr:solr-core☕org.apache.solr:solr-core☕org.apache.solr:solr-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Remote code execution occurs in Apache Solr before 7.1 with Apache Lucene before 7.1 by exploiting XXE in conjunction with use of a Config API add-listener command to reach the RunExecutableListener class. Elasticsearch, although it uses Lucene, is NOT vulnerable to this. Note that the XML external entity expansion vulnerability occurs in the XML Query Parser which is available, by default, for any query request with parameters deftype=xmlparser and can be exploited to upload malicious data to the /upload request handler or as Blind XXE using ftp wrapper in order to read arbitrary local files from the Solr server. Note also that the second vulnerability relates to remote code execution using the RunExecutableListener available on all affected versions of Solr.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.solr:solr-core | ≥ 7.0.0&&< 7.1.0 | 7.1.0org.apache.solr:solr-core:7.1.0 |
| ☕Maven | org.apache.solr:solr-core | ≥ 6.0.0&&< 6.6.2 | 6.6.2org.apache.solr:solr-core:6.6.2 |
| ☕Maven | org.apache.solr:solr-core | ≥ 5.5.0&&< 5.5.5 | 5.5.5org.apache.solr:solr-core:5.5.5 |
Affected Products
solrapacheubuntu linuxcanonicaldebian linuxdebianjboss enterprise application platformredhatResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Apache Solr 7.0.1 - XML External Entity Expansion / Remote Code Execution
by Michael Stepankin & Olga Barinova · Oct 17, 2017
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.solr:solr-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.solr:solr-core to 7.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-12629 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How to detect CVE-2017-12629
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2017-12629 -u https://target- Template
- Apache Solr <= 7.1 - XML Entity Injection
- Severity
- critical
- Impact
- Successful exploitation of this vulnerability could lead to information disclosure, denial of service.
- Remediation
- Upgrade to a patched version of Apache Solr (7.2 or higher) or apply the recommended security patches.
Template by ProjectDiscovery nuclei-templates (dwisiswant0), MIT licensed. View the full template. Scan only systems you are authorised to test.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The following products are not affected by this flaw, as they do not use the vulnerable functionality of either aspect of the issue. Red Hat JBoss Enterprise Application Platform 6 Red Hat JBoss BPM Suite Red Hat JBoss BRMS Red Hat Enterprise Virtualization Manager Red Hat Single Sign-On 7 Red Hat JBoss Portal…
Until fixes are available, all Solr users are advised to restart their Solr instances with the system parameter `-Ddisable.configEdit=true`. This will disallow any changes to be made to configurations via the Config API. This is a key factor in this vulnerability, since it allows GET requests to add the RunExecutableListener to the config. This is sufficient to protect from this type of attack, but means you cannot use the edit capabilities of the Config API until further fixes are in place.Source: Red Hat security advisory for CVE-2017-12629 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat JBoss Data Grid 7.1 | see advisory | RHSA-2017:3244 |
| Red Hat JBoss EAP 7 | lucene-core | RHSA-2018:0003 |
| Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 6 | eap7-lucene-solr-0:5.3.1-4.redhat_2.1.ep7.el6 | RHSA-2017:3123 |
| Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 6 | eap7-activemq-artemis-0:1.1.0-19.SP24_redhat_1.1.ep7.el6 | RHSA-2018:0002 |
| Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 6 | eap7-jboss-ec2-eap-0:7.0.9-2.GA_redhat_2.ep7.el6 | RHSA-2018:0005 |
| Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 7 | eap7-activemq-artemis-0:1.1.0-19.SP24_redhat_1.1.ep7.el7 | RHSA-2018:0004 |
| Red Hat JBoss Enterprise Application Platform 7.0 security update | see advisory | RHSA-2017:3124 |
| Red Hat JBoss Enterprise Application Platform Continuous Delivery | lucene | RHSA-2020:2561 |
Frequently Asked Questions
Is CVE-2017-12629 in your dependencies?
Find it across Maven, including transitive dependencies.