CVE-2019-0193Apache Solr DataImportHandler Code Injection Vulnerability

Patch nowHigh7.2ExploitedEPSS 84%

CVE-2019-0193 is a code injection in Apache Solr, rated high (7.2 on CVSS 3.1).

Why this priority: Exploited in the wild: listed in CISA's KEV catalog.

Published 1 Aug 2019 · Updated 17 Jun 2026 · NVD status: Analyzed

What it is

Input is evaluated as code by the application, so an attacker's code runs inside it.

How it is reached

An attacker can exploit it over the network, with an administrator account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker run commands or code with the privileges of the affected service.

Is it being exploited?

CISA added it to the Known Exploited Vulnerabilities catalog on 2021-12-10: it is being exploited in the wild. EPSS estimates a 84% chance of exploitation activity in the next 30 days, higher than 100% of scored CVEs.

What to do

Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2022-06-10.
Upgrade Apache Solr to a fixed version for your release line (7.7.3, 8.1.2). The patch notes are linked below.
Until it is patched, review who holds accounts that can reach it.
Check exposed instances for signs of compromise, not only for the version.

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

Operating systems on servers, workstations or devices. Everything on the host inherits the flaw.
Application servers and the hosts they run on. The flaw sits between untrusted input and code or command execution.
Template engines. The flaw sits between untrusted input and code or command execution.

Trust boundaries in play

Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
Between untrusted input and code or command execution. An attacker who crosses it can run commands or code with the privileges of the affected service.

Questions to answer about your own systems

Where does Apache Solr run in your systems, and at which version?
Which of those instances can be reached from the internet or partner networks?
What can it reach once compromised: which data stores, secrets and services?

See how Veriom maps an architecture Take the interactive tour

Patches and commits

Advisories

Issue reports

Sources

CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.