Skip to content

GHSA-mh7g-99w9-xpjm CVE-2017-12629

Remote code execution occurs in Apache Solr

Critical Maven
Severity
9.8 / 10
Critical · CVSS 3.1
Exploit chance (EPSS)
91.90%
Chance of exploitation in the next 30 days. Higher than 99.82% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-611 Improper Restriction of XML External Entity Reference
Fix
7.1.0
Upgrade org.apache.solr:solr-core to this version or later

Description

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

Affected versions

Maven

PackageVulnerableFixed in
org.apache.solr:solr-core
>= 7.0.0, < 7.1.0
7.1.0
org.apache.solr:solr-core
>= 6.0.0, < 6.6.2
6.6.2
org.apache.solr:solr-core
>= 5.5.0, < 5.5.5
5.5.5

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.apache.solr:solr-core Maven → 7.1.0

maven
<dependency><groupId>org.apache.solr</groupId><artifactId>solr-core</artifactId><version>7.1.0</version></dependency>
gradle
implementation("org.apache.solr:solr-core:7.1.0")

Severity breakdown

CVSS 3.1 9.8

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-611: Improper Restriction of XML External Entity Reference

The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

How to prevent it
  • Implementation, System Configuration: Many XML parsers and validators can be configured to disable external entity expansion.

References

Advisories

Packages

Other links

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
CVE-2019-17558
Improper Input Validation in Apache Solr
High Known exploited Also affects org.apache.solr:solr-core
CVE-2019-0193
XML External Entity (XXE) Injection in Apache Solr
High Known exploited Also affects org.apache.solr:solr-core
GHSA-qhr7-h655-pw6r
Apache Solr has hardcoded credentials in the Basic Authentication setup tool
Critical Also affects org.apache.solr:solr-core
GHSA-vc2w-4v3p-2mqw
Apache Solr: Insufficient file-access checking in standalone core-creation requests
High Also affects org.apache.solr:solr-core
GHSA-qr3p-2xj2-q7hq
Apache Solr: Unauthorized bypass of certain "predefined permission" rules in the RuleBasedAuthorizationPlugin
High Also affects org.apache.solr:solr-core
GHSA-68r2-fwcg-qpm8
Apache Solr vulnerable to Execution with Unnecessary Privileges
Medium Also affects org.apache.solr:solr-core
GHSA-4p5m-gvpf-f3x5
Apache Solr Relative Path Traversal vulnerability
Medium Also affects org.apache.solr:solr-core
GHSA-37vr-vmg4-jwpw
Apache Solr: Backup/Restore APIs allow for deployment of executables in malicious ConfigSets
High Also affects org.apache.solr:solr-core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor