CVE-2017-12629: XEE

Published Oct 12, 2017
·
Updated

It was found that Apache Solr would accept an object from an unauthenticated user that could be manipulated through subsequent post requests. An attacker could use this flaw to assemble an object that could permit execution of arbitrary code on the server.

Other sources

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.

Launchpad

Remote code execution occurs in Apache Solr before versions 5.5.5, 6.6.2 and 7.1.0 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

GitHub

Affected Software

23 affected componentsFixes available
maven/org.apache.solr:solr-core>=5.5.0<5.5.5
5.5.5
maven/org.apache.solr:solr-core>=6.0.0<6.6.2
6.6.2
maven/org.apache.solr:solr-core>=7.0.0<7.1.0
7.1.0
Apache Solr>=5.5.0<=5.5.4
Apache Solr>=6.0.0<=6.6.1
Apache Solr>=7.0.0<=7.0.1
redhat JBoss Enterprise Application Platform=7.0.0
redhat JBoss Enterprise Application Platform=7.1.0
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Server=7.0
Debian Debian Linux=7.0
Debian Debian Linux=8.0
Debian Debian Linux=9.0
Canonical Ubuntu Linux=16.04
redhat/lucene-solr<5.5.5
5.5.5
redhat/lucene-solr<6.6.2
6.6.2
redhat/lucene-solr<7.1
7.1
redhat/lucene-solr<8.0
8.0
All of the following
Any of the following
redhat JBoss Enterprise Application Platform=7.0.0
redhat JBoss Enterprise Application Platform=7.1.0
Any of the following
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Server=7.0
debian/lucene-solr
3.6.2+dfsg-243.6.2+dfsg-263.6.2+dfsg-27

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.solr:solr-core to a version that resolves this vulnerability.

    Fixed in 5.5.5
  2. Upgrade

    Upgrade maven/org.apache.solr:solr-core to a version that resolves this vulnerability.

    Fixed in 6.6.2
  3. Upgrade

    Upgrade maven/org.apache.solr:solr-core to a version that resolves this vulnerability.

    Fixed in 7.1.0
  4. Upgrade

    Upgrade debian/lucene-solr to a version that resolves this vulnerability.

    Fixed in 3.6.2+dfsg-24Fixed in 3.6.2+dfsg-26Fixed in 3.6.2+dfsg-27
  5. Upgrade

    Upgrade redhat/lucene-solr to a version that resolves this vulnerability.

    Fixed in 5.5.5
  6. Upgrade

    Upgrade redhat/lucene-solr to a version that resolves this vulnerability.

    Fixed in 6.6.2
  7. Upgrade

    Upgrade redhat/lucene-solr to a version that resolves this vulnerability.

    Fixed in 7.1
  8. Upgrade

    Upgrade redhat/lucene-solr to a version that resolves this vulnerability.

    Fixed in 7.2
  9. Upgrade

    Upgrade redhat/lucene-solr to a version that resolves this vulnerability.

    Fixed in 8.0
  10. Upgrade

    Upgrade Apache Solr to a version that resolves this vulnerability.

    Fixed in 5.5.5
  11. Upgrade

    Upgrade Apache Solr to a version that resolves this vulnerability.

    Fixed in 6.6.2
  12. Upgrade

    Upgrade Apache Solr to a version that resolves this vulnerability.

    Fixed in 7.1.0
  13. Compensating control

    If Solr is exposed, restrict access so unauthenticated users cannot submit XML query requests that use deftype=xmlparser and cannot reach the /upload request handler.

Event History

Oct 12, 2017
Data Sourced
via Red Hat·07:11 PM
DescriptionSeverityAffected Software
Oct 14, 2017
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
DescriptionWeakness
Data Sourced
via NVD·11:29 PM
DescriptionSeverityWeaknessAffected Software
Oct 17, 2018
Advisory Published
via GitHub·07:56 PM
Feb 19, 2026
Data Sourced
via Ubuntu·08:34 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Launchpad·08:35 PM
Description
Data Sourced
via Debian·08:35 PM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2017-12629?

CVE-2017-12629 has been classified as a critical security vulnerability due to its ability to allow remote code execution.

2

How do I fix CVE-2017-12629?

To remediate CVE-2017-12629, upgrade to the patched versions of Apache Solr as specified in the vulnerability details.

3

What types of software are affected by CVE-2017-12629?

CVE-2017-12629 affects several versions of Apache Solr, including multiple releases of Lucene-Solr across Debian, Red Hat, and Ubuntu distributions.

4

What can an attacker do with CVE-2017-12629?

An attacker exploiting CVE-2017-12629 can manipulate objects sent by unauthenticated users, potentially leading to arbitrary code execution on the server.

5

Are there any known exploits for CVE-2017-12629?

Yes, CVE-2017-12629 has been publicly disclosed, which makes it imperative for users to address the vulnerability without delay.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203