dbcve.org
SolrApplication · Apache

CVE-2017-12629

CRITICAL · 9.8 CVSS v3.1 Published 2017-10-14
Fix available
A fix is available. Upgrade to after 7.0.1 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-611

An XML parser processes external entity references inside untrusted documents, letting an attacker read local files, reach internal systems, or exhaust resources. It's a common trap in anything that accepts XML. The fix is to disable external entities and DTD processing in the parser.

General guidance for the xml external entity (xxe) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SolrApplication
Affected:>= 5.5.0, <= 5.5.4>= 6.0.0, <= 6.6.1>= 7.0.0, <= 7.0.1
Jboss Enterprise Application PlatformApplication
Affected:= 7.0.0= 7.1.0
Debian LinuxOperating system
Affected:= 7.0= 8.0= 9.0
Ubuntu LinuxOperating system
Affected:= 16.04

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 7.0.1
Recommended fix High confidence

Apache Solr 7.1.0 or later (preferably latest stable 7.x/8.x/9.x release)

  1. 1. Identify the current Apache Solr version by checking the solr-solrj or lucene-core JAR files in the installation directory, or by querying the Solr admin API at /solr/admin/info/system
  2. 2. Stop the Solr service to prevent data corruption during upgrade
  3. 3. Create a complete backup of the Solr data directory (typically $SOLR_HOME/data) and configuration files in $SOLR_HOME/server/solr
  4. 4. Download Apache Solr 7.1.0 or later from the official Apache repository (archive.apache.org/dist/lucene/solr/)
  5. 5. Extract the new Solr binary distribution to the target installation directory
  6. 6. Copy the backed-up configuration and data to the new installation
  7. 7. Verify that the XML Query Parser (deftype=xmlparser) is not exposed or is properly restricted if not needed in production
  8. 8. Start the Solr service and verify it launches successfully
Caveat Upgrading major versions (e.g., 5.x to 7.x) may require configuration changes; test thoroughly in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $3,550. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-12629 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-12629 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data