Patchfirst
CVE-2017-12629 Public exploit EPSS 91.9%

Remote code execution occurs in Apache Solr before 7.1 with Apache Lucene before 7.1 by exploiting XXE in conjunction…

Summary

Apache Solr before 7.1 (built on Apache Lucene before 7.1) contains an XML external entity (XXE) flaw in its XML Query Parser, which is enabled by default, and remote code execution is possible by combining XXE with the Config API add-listener command to reach the RunExecutableListener class. An attacker who can send query requests with deftype=xmlparser can use the XXE to upload malicious data to the /upload request handler or read arbitrary local files via a blind XXE over the ftp wrapper, and the RunExecutableListener route reaches code execution on all affected Solr versions.

Official description · CVE.org

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.

Breakdown
26.3 / 100
Exploited
Not confirmed
Reports
0
Tactics
0/15

Public exploit code (Exploit-DB) appeared 3 days after disclosure. No confirmed exploitation is recorded.

  1. Disclosedday 0
  2. Public exploit codeExploit-DB+3 days

8 fixes in solr-core over 20 months. The latest fix listed for solr-core is 7.4.0.

Fixes in solr-coreMaven package, by fixed version. Earlier and later fixes in the same package, not necessarily the same bug.

  1. 6.4.1CVE-2017-316330 Aug 2017
  2. 6.6.0CVE-2017-76607 Jul 2017
  3. 6.6.1CVE-2017-980318 Sep 2017
  4. 7.0.0CVE-2019-01927 Mar 2019
  5. 7.1.0CVE-2017-1262914 Oct 2017
  6. 7.3.0CVE-2018-13089 Apr 2018
  7. 7.3.1CVE-2018-801021 May 2018
  8. 7.4.0CVE-2018-80265 Jul 2018Latest listed

techniques

No techniques linked

No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

1 package in 1 ecosystem. Main package: org.apache.solr:solr-core.

Mavenorg.apache.solr:solr-coreGHSA-mh7g-99w9-xpjm

Upgrade to 7.1.0

Still affected on this line by CVE-2019-0193 (fixed in 8.2.0, a newer line); CVE-2019-17558 (fixed in 8.4.0, a newer line); CVE-2020-13957 (fixed in 8.6.3, a newer line); CVE-2023-50386 (fixed in 8.11.3, a newer line).

Set the version to 7.1.0 or later in your pom.xml or build.gradle.

The first fix for CVE-2017-12629.

Affected versions, by release line

If you runUpgrade to
7.0.0 up to 7.1.07.1.0
6.0.0 up to 6.6.2

Still affected on this line by CVE-2019-0192 (fixed in 7.0.0, a newer line); CVE-2019-0193 (fixed in 8.2.0, a newer line); CVE-2019-17558 (fixed in 8.4.0, a newer line); CVE-2020-13957 (fixed in 8.6.3, a newer line); CVE-2023-50386 (fixed in 8.11.3, a newer line).

6.6.2
5.5.0 up to 5.5.5

Still affected on this line by CVE-2019-0192 (fixed in 7.0.0, a newer line); CVE-2019-0193 (fixed in 8.2.0, a newer line); CVE-2019-17558 (fixed in 8.4.0, a newer line).

5.5.5

“Up to” means the second version is the fix and is not affected.

Check your lockfile against all CVEs

What security researchers reported

Not named in any threat report yet

Also mentioned in 3 community threat pulses (AlienVault OTX)

Weaker evidence

Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.

References

24 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close