dbcve.org
SolrApplication · Apache

CVE-2019-0192

CRITICAL · 9.8 CVSS v3.0 Published 2019-03-07
Fix available
A fix is available. Upgrade to after 6.6.5 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges Zero-click

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 versions 5.0.0 to 5.5.5 and 6.0.0 to 6.6.5, the Config API allows to configure the JMX server via an HTTP POST request. By pointing it to a malicious RMI server, an attacker could take advantage of Solr's unsafe deserialization to trigger remote code execution on the Solr side.

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 Config API in versions 5.0.0-5.5.5 and 6.0.0-6.6.5 allows configuring the JMX server via HTTP POST. An attacker can point this to a malicious RMI server to exploit unsafe deserialization, achieving remote code execution on the Solr instance.

MitigationUpgrade to Apache Solr 5.5.6 or 6.6.6 and later, which contain the fix for this vulnerability. Alternatively, disable or restrict JMX/remote RMI access and network-segment the Solr service.

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:>= 5.0.0, <= 5.5.5>= 6.0.0, <= 6.6.5
Storage Automation StoreApplication
Affected:all versions

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 installed Solr version
    Run: bin/solr version or check the solr-$VERSION.jar file in the installation directory, or query the Solr API at /solr/admin/info/system
    Affected if The version is 5.0.0-5.5.5 or 6.0.0-6.6.5, indicating the instance has the vulnerable Config API
  2. Verify if Config API accepts JMX configuration
    Send a POST request to /solr/<collection>/config with a body containing JMX-related settings such as {"set-property":{"jmx":{"serviceUrl":"service:jmx:rmi://localhost:18983"}}}. Inspect the response for success or error messages indicating whether JMX configuration is allowed.
    Affected if The Config API accepts and applies JMX configuration changes, enabling an attacker to redirect the JMX service URL
  3. Check if JMX port is exposed or accessible
    Run netstat -an | grep 18983 or ss -tlnp | grep 18983 to see if the default JMX port (18983) is listening. Also check if the Solr process has JMX beans enabled by examining JMX-related logs or MBeans.
    Affected if The JMX port 18983 is open and reachable, or JMX is enabled in the Solr configuration, allowing deserialization attacks via RMI
  4. Assess network exposure of Solr services
    Review firewall rules and network segmentation around the Solr host. Determine if the Solr HTTP API (port 8983 by default) and JMX port are accessible from untrusted networks or the internet.
    Affected if Solr HTTP or JMX ports are accessible from untrusted network segments, increasing exploitability

You are affected if you run Apache Solr versions 5.0.0-5.5.5 or 6.0.0-6.6.5 (or any Netapp Storage Automation Store version) and the Config API accepts JMX configuration or JMX ports are network-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 a release after 6.6.5
Interim mitigation

Upgrade to Apache Solr 5.5.6 or 6.6.6 and later, which contain the fix for this vulnerability. Alternatively, disable or restrict JMX/remote RMI access and network-segment the Solr service.

Recommended fix High confidence

Solr 5.6.0+ for 5.x branch, or Solr 6.7.0+/7.x for 6.x branch

  1. 1. Backup your current Solr configuration and data directories before any upgrade
  2. 2. Identify your current Solr version by checking the version.txt file in the Solr home directory or running: bin/solr version
  3. 3. If running Solr 5.x (5.0.0 to 5.5.5), upgrade to Solr 5.6.0 or later
  4. 4. If running Solr 6.x (6.0.0 to 6.6.5), upgrade to Solr 6.7.0 or later (preferably 7.x)
  5. 5. After upgrade, verify the Config API no longer allows unauthenticated JMX server configuration
  6. 6. If upgrading is not immediately possible, disable the Config API or restrict access to it via network segmentation and authentication
Caveat Major version upgrades (e.g., 5.x to 6.x, 6.x to 7.x) may require configuration changes and index format upgrades; test in staging first

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

Fix this in Solr Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-0192 — 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-0192 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