Skip to content

XML External Entity (XXE) Injection in Apache Solr

High severity GitHub Reviewed Published Aug 1, 2019 to the GitHub Advisory Database • Updated Jul 25, 2024

Package

maven org.apache.solr:solr-core (Maven)

Affected versions

< 8.2.0

Patched versions

8.2.0

Description

In Apache Solr, the DataImportHandler, an optional but popular module to pull in data from databases and other sources, has a feature in which the whole DIH configuration can come from a request's "dataConfig" parameter. The debug mode of the DIH admin screen uses this to allow convenient debugging / development of a DIH config. Since a DIH config can contain scripts, this parameter is a security risk. Starting with version 8.2.0 of Solr, use of this parameter requires setting the Java System property "enable.dih.dataConfigParam" to true.

References

Published by the National Vulnerability Database Aug 1, 2019
Reviewed Aug 1, 2019
Published to the GitHub Advisory Database Aug 1, 2019
Last updated Jul 25, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

EPSS score

93.505%
(99th percentile)

Weaknesses

CVE ID

CVE-2019-0193

GHSA ID

GHSA-3gm7-v7vw-866c

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.