CVE-2019-0193
HighExploitedPublic exploitXML External Entity (XXE) Injection in Apache Solr
Published Aug 1, 2019 · Updated Aug 4, 2026 · Also known as DEBIAN-CVE-2019-0193, DLA-1954-1, DLA-2327-1, GHSA-3gm7-v7vw-866c, UBUNTU-CVE-2019-0193
Key Facts
Patch immediately- CVE-2019-0193 is a high-severity vulnerability (CVSS 7.2 v3.1) affecting Solr (Apache), Debian Linux, lucene-solr (debian) and 1 more product.
- It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Jan 16, 2020. Public exploit code is available.
- EPSS estimates a 84% probability of exploitation in the next 30 days.
- Fixed versions are available, including Solr 7.7.3, lucene-solr 3.6.2+dfsg-10+deb9u3, lucene-solr 3.6.2+dfsg-18~18.04.1~esm2.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
7.2
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
84%
Higher than 99.6% of all scored CVEs
Exploited in the wild
Yes
4 catalog listings
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2019-0193 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
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.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| CISA KEV | Dec 10, 2021 | Jun 10, 2022 | Not reported |
| Industry KEV feed | Jan 16, 2020 | Jun 10, 2022 | Not reported |
| CIRCL KEV | Dec 10, 2021 | Jun 10, 2022 | Not reported |
| ENISA EUVD | Dec 10, 2021 | n/a | Not reported |
Required action: Apply updates per vendor instructions.
Affected Products
19 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| SolrApache | >= Apache Solr all prior to 8.2.0 | 7.7.3 |
| Debian LinuxDebian | 8.0, 9.0 | n/a |
| lucene-solrdebian | See advisory | 3.6.2+dfsg-22 |
| org.apache.solr:solr-coremaven | See advisory | 8.2.0 |
Patched Releases
Solr
7.7.3
lucene-solr
3.6.2+dfsg-10+deb9u3, 3.6.2+dfsg-18~18.04.1~esm2, 3.6.2+dfsg-22, 3.6.2+dfsg-2ubuntu0.1~esm4, 3.6.2+dfsg-5+deb8u3, 3.6.2+dfsg-8ubuntu0.1+esm1
org.apache.solr:solr-core
8.2.0
Timeline
Publicly disclosed
Aug 1, 2019
Added to Industry KEV feed
Jan 16, 2020
Added to CISA KEV
Dec 10, 2021
Added to CIRCL KEV
Dec 10, 2021
Added to ENISA EUVD
Dec 10, 2021
Last updated
Aug 4, 2026
Weakness Type
- CWE-20 Improper Input Validation
- CWE-94 Improper Control of Generation of Code ('Code Injection')
References
- advisoryGHSA advisory
- advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2019-0193
- advisoryhttps://security-tracker.debian.org/tracker/CVE-2019-0193
- advisoryhttps://ubuntu.com/security/CVE-2019-0193
- advisoryhttps://ubuntu.com/security/notices/USN-7283-1
FAQ
Common Questions.
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.
Affected: Solr (Apache) versions >= Apache Solr all prior to 8.2.0; Debian Linux versions 8.0, 9.0; lucene-solr (debian), among others. The full list is in the CVE brief.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Jan 16, 2020.
Yes. It was added on Dec 10, 2021 with a federal remediation due date of Jun 10, 2022.
Public exploit code is available.
Fixed versions are available, including Solr 7.7.3, lucene-solr 3.6.2+dfsg-10+deb9u3, lucene-solr 3.6.2+dfsg-18~18.04.1~esm2.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2019-0193 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo