CVE-2019-0193

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Apache Solr. For every flaw being used in attacks, see Exploited flaws; for Apache’s, see Apache flaws being used in attacks.

CVE-2019-0193 is a security flaw in Apache Solr, open-source software from the Apache Software Foundation. Attackers can run their own code on Apache Solr. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 10 Dec 2021.[1]

Apache Solr is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Apache has published a fix or advice.

Description

CISA calls it a dataImportHandler code injection in Apache Solr. In its words: “The optional Apache Solr module DataImportHandler contains a code injection vulnerability.”[1]

The CVE record adds: “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.”[2]

The underlying weakness is code injection (CWE-94), in MITRE’s list of common software weaknesses.

It scores 7.2 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by NVD using CVSS 3.1.[2]

Affected versions

NVD’s record doesn’t list version ranges for it; Apache’s advisory has them[3]. CISA names the product as Apache Solr.

Most families won’t have Apache Solr; it’s for whoever looks after IT at work.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 10 Dec 2021, 862 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 10 Jun 2022 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 84%. That’s in the top 1% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

Apache has published a fix or advice.[3] CISA’s required action: “Apply updates per vendor instructions.”[1]

  1. Check whether you use it.Apache Solr is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
  2. Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 10 Jun 2022 to fix it.
  3. If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.

You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 7.2.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at 84%.[4]

See also

Other Apache Solr flaws

  • CVE-2019-17558: velocityResponseWriter plug-in remote code execution ·

Other Apache flaws

  • CVE-2016-3081, Apache Struts: command injection ·
  • CVE-2026-34486, Apache Tomcat: missing encryption of sensitive data ·
  • CVE-2026-34197, Apache ActiveMQ: improper input validation ·
  • CVE-2024-38475, Apache HTTP Server: improper escaping of output ·
  • CVE-2025-24813, Apache Tomcat: path equivalence ·

Other code injection flaws

Added the same day

  • CVE-2021-44515, Zoho Desktop Central: authentication bypass ·
  • CVE-2021-44228, Apache Log4j2: remote code execution ·
  • CVE-2021-44168, Fortinet FortiOS: arbitrary file download ·
  • CVE-2021-35394, Realtek Jungle Software Development Kit (SDK): jungle SDK remote code execution ·
  • CVE-2020-8816, Pi-hole AdminLTE: remote code execution ·

Every Apache flaw on CISA’s list · Everything added in December 2021

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Apache Solr DataImportHandler Code Injection Vulnerability”. Known Exploited Vulnerabilities Catalog, added 10 Dec 2021.
  2. ^ National Institute of Standards and Technology. “CVE-2019-0193 Detail”. National Vulnerability Database, published 1 Aug 2019.
  3. ^ Apache. Advisories and fixes: issues.apache.org, lists.apache.org, lists.apache.org.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.835, percentile 99.7, 31 Oct 2026.
  5. CVE Program. “CVE-2019-0193”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.