dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 10 Jun 2022.
SolrApplication · Apache

CVE-2019-0193

HIGH · 7.2 CVSS v3.1 Published 2019-08-01
Fix available
A fix is available. Upgrade to 7.7.3 / 8.1.2 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Solr's DataImportHandler (DIH) module allows configuration to be passed via the 'dataConfig' request parameter, which can contain scripts. This enables remote code execution by malicious actors who can inject arbitrary script content through this parameter. The debug mode on the DIH admin screen was the primary attack vector.

MitigationSet the Java System property 'enable.dih.dataConfigParam' to true only when absolutely required, and preferably upgrade to Solr 8.2.0+ where this dangerous feature is disabled by default. If DIH is unused, consider disabling the DataImportHandler entirely.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SolrApplication
Affected:< 7.7.3>= 8.1.0, < 8.1.2
Debian LinuxOperating system
Affected:= 8.0= 9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the DataImportHandler request handler
    Examine your Solr configuration files (solrconfig.xml) for a request handler definition with '/dataimport' as the path. This indicates DIH is enabled.
    Affected if A '/dataimport' request handler exists in your Solr configuration
  2. Determine the installed Solr version
    Run 'bin/solr version' from your Solr installation directory, or check the VERSION.txt file in the Solr home directory.
    Affected if The version is less than 7.7.3, OR greater than or equal to 8.1.0 but less than 8.1.2
  3. Check if the dataConfig parameter is enabled
    Inspect your Solr startup scripts or solr.in.sh/solr.in.cmd for the Java system property '-Denable.dih.dataConfigParam=true', or check the Java runtime properties.
    Affected if The property 'enable.dih.dataConfigParam' is set to 'true' in your Solr configuration
  4. Verify DIH debug endpoint accessibility
    Attempt to access the DataImportHandler debug screen at '/solr/{core}/dataimport?debug=true&command=full-import' on your Solr instance.
    Affected if The debug mode is accessible and accepts the 'dataConfig' parameter input
  5. Confirm DIH is actually deployed
    List all loaded request handlers via the Solr admin UI or API endpoint '/solr/admin/info/system' to verify DIH is present and active.
    Affected if DataImportHandler appears in the list of loaded request handlers

You are affected if your Solr version falls within the vulnerable range AND DataImportHandler is enabled with the dataConfig parameter feature accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.7.3 / 8.1.2 or later
Fixed in 7.7.38.1.2
Vendor patch lists.apache.org →
Interim mitigation

Set the Java System property 'enable.dih.dataConfigParam' to true only when absolutely required, and preferably upgrade to Solr 8.2.0+ where this dangerous feature is disabled by default. If DIH is unused, consider disabling the DataImportHandler entirely.

Recommended fix High confidence

Solr 8.2.0 (or 7.7.3+ / 8.1.2+ as needed)

  1. 1. Identify your current Solr version by checking the Solr admin UI or running 'bin/solr version'
  2. 2. Plan an upgrade to Solr 8.2.0 or later for the most stable and secure release (or alternatively 7.7.3 if staying on the 7.x branch, or 8.1.2 if staying on the 8.1.x branch)
  3. 3. Before upgrading, backup your Solr configuration and data directories
  4. 4. Download the target version from https://solr.apache.org/downloads.html
  5. 5. Stop the running Solr instance
  6. 6. Install the new version following the standard upgrade procedure
  7. 7. Start Solr and verify the DataImportHandler works correctly
  8. 8. Confirm the vulnerability is fixed by verifying that the 'dataConfig' parameter is blocked without explicitly enabling it via the 'enable.dih.dataConfigParam' system property
Caveat Review release notes for breaking changes between your current version and target version; major version upgrades may require configuration adjustments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Solr Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-0193 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-0193 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data