# What is CVE-2017-12629?

> CVE-2017-12629 is a critical-severity flaw (CVSS 9.8) in Solr from Apache, published on 14 October 2017. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 92%. If you run an affected version, plan in the vendor’s fix.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2017-12629

## At a glance

- **Verdict:** Fix this soon. Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
- **Precursor Intelligence risk score:** 71 out of 100 (High); action: Patch now. Kept up to date as the evidence changes.
- **Severity:** Critical (CVSS 9.8 out of 10)
- **Known to be exploited:** No, not on the list of flaws known to be exploited today
- **Chance of use in the next 30 days:** 92% (latest exploit-likelihood forecast)
- **Published:** 14 October 2017
- **Record last updated:** 20 April 2025
- **Main product:** Solr from Apache
- **Affected products:** 5

## What is CVE-2017-12629? In plain terms

It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

### The official 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.

### What kind of flaw is it?

- CWE-611: Improper Restriction of XML External Entity Reference

### How an attack on it works

- Where an attacker can be: Anywhere on the internet
- How hard it is to pull off: Easy: no special conditions
- Login needed first: No login needed
- Does someone have to click: No, nobody has to do anything
- What an attacker gets: Can read data, change data and take it offline

Severity vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`

## Is CVE-2017-12629 being exploited? Not that we know of

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 92%. That can change at any time, which is why we keep watching.

Exploit likelihood over the last 7 days: 92%, 92%, 92%, 92%, 92%, 92%, 92%.

### Timeline

- 14 October 2017: Published
- 20 April 2025: Record last updated

### How Precursor Intelligence ranks it

CVE-2017-12629 scores **71 out of 100 (High)**, with the action "Patch now".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: smaller factor
- Threat activity around it: smaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2017-12629?

The published record lists 5 products.

- [Solr](https://www.precursorintelligence.com/product/apache/solr) by [Apache](https://www.precursorintelligence.com/vendors/apache) (Application): 5.5.0 to 5.5.4, 6.0.0 to 6.6.1, 7.0.0 to 7.0.1
- [Debian Linux](https://www.precursorintelligence.com/product/debian/debian_linux) by [Debian](https://www.precursorintelligence.com/vendors/debian) (Operating system): 7.0, 8.0, 9.0
- [Enterprise Linux Server](https://www.precursorintelligence.com/product/redhat/enterprise_linux_server) by [Red Hat](https://www.precursorintelligence.com/vendors/redhat) (Operating system): 6.0, 7.0
- [Jboss Enterprise Application Platform](https://www.precursorintelligence.com/product/redhat/jboss_enterprise_application_platform) by [Red Hat](https://www.precursorintelligence.com/vendors/redhat) (Application): 7.0.0, 7.1.0
- [Ubuntu Linux](https://www.precursorintelligence.com/product/canonical/ubuntu_linux) by [Canonical](https://www.precursorintelligence.com/vendors/canonical) (Operating system): 16.04

## How do I fix CVE-2017-12629?

1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

### References

- [mail-archives.us.apache.org](http://mail-archives.us.apache.org/mod_mbox/www-announce/201710.mbox/%3CCAOOKt51UO_6Vy%3Dj8W%3Dx1pMbLW9VJfZyFWz7pAnXJC_OAdSZubA%40mail.gmail.com%3E) (Mailing list, Vendor advisory)
- [s.apache.org](https://s.apache.org/FJDl) (Exploit, Mailing list, Vendor advisory)
- [openwall.com](http://openwall.com/lists/oss-security/2017/10/13/1) (Mailing list, Third-party advisory)
- [securityfocus.com](http://www.securityfocus.com/bid/101261) (Third-party advisory, Vulnerability database)
- [access.redhat.com](https://access.redhat.com/errata/RHSA-2017:3123) (Third-party advisory)
- [access.redhat.com](https://access.redhat.com/errata/RHSA-2017:3124) (Third-party advisory)
- [access.redhat.com](https://access.redhat.com/errata/RHSA-2017:3244) (Third-party advisory)
- [access.redhat.com](https://access.redhat.com/errata/RHSA-2017:3451) (Third-party advisory)
- [access.redhat.com](https://access.redhat.com/errata/RHSA-2017:3452) (Third-party advisory)
- [access.redhat.com](https://access.redhat.com/errata/RHSA-2018:0002) (Third-party advisory)
- [access.redhat.com](https://access.redhat.com/errata/RHSA-2018:0003) (Third-party advisory)
- [access.redhat.com](https://access.redhat.com/errata/RHSA-2018:0004) (Third-party advisory)
- [access.redhat.com](https://access.redhat.com/errata/RHSA-2018:0005) (Third-party advisory)
- [lists.apache.org](https://lists.apache.org/thread.html/r140128dc6bb4f4e0b6a39e962c7ca25a8cbc8e48ed766176c931fccc%40%3Cusers.solr.apache.org%3E)
- [lists.apache.org](https://lists.apache.org/thread.html/r26c996b068ef6c5e89aa59acb769025cfd343a08e63fbe9e7f3f720f%40%3Coak-issues.jackrabbit.apache.org%3E)
- [lists.apache.org](https://lists.apache.org/thread.html/r3da74965aba2b5f5744b7289ad447306eeb2940c872801819faa9314%40%3Cusers.solr.apache.org%3E)
- [lists.apache.org](https://lists.apache.org/thread.html/r95df34bb158375948da82b4dfe9a1b5d528572d586584162f8f5aeef%40%3Cusers.solr.apache.org%3E)
- [lists.debian.org](https://lists.debian.org/debian-lts-announce/2018/01/msg00028.html) (Mailing list, Third-party advisory)
- [twitter.com](https://twitter.com/ApacheSolr/status/918731485611401216) (Third-party advisory)
- [twitter.com](https://twitter.com/joshbressers/status/919258716297420802) (Third-party advisory)
- [twitter.com](https://twitter.com/searchtools_avi/status/918904813613543424) (Third-party advisory)
- [usn.ubuntu.com](https://usn.ubuntu.com/4259-1/) (Third-party advisory)
- [debian.org](https://www.debian.org/security/2018/dsa-4124) (Third-party advisory)
- [exploit-db.com](https://www.exploit-db.com/exploits/43009/) (Exploit, Third-party advisory, Vulnerability database)

## Questions

### What is CVE-2017-12629?

CVE-2017-12629 is a critical-severity flaw in Solr from Apache, published on 14 October 2017. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

### How serious is CVE-2017-12629?

It scores 9.8 out of 10 on the CVSS severity scale, which is critical. Our risk score for CVE-2017-12629 is 71 out of 100, which is High. Its action is "Patch now". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.

### Is CVE-2017-12629 being exploited?

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 92%. That can change at any time, which is why we keep watching.

### Which versions does CVE-2017-12629 affect?

For Solr from Apache: 5.5.0 to 5.5.4, 6.0.0 to 6.6.1, 7.0.0 to 7.0.1. The record lists 5 products in all, each with its versions, under "Who is affected" on this page.

### How do I fix CVE-2017-12629?

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

## Does CVE-2017-12629 affect you?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact