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 3 May 2022.
SolrApplication · Apache

CVE-2019-17558

HIGH · 7.5 CVSS v3.1 Published 2019-12-30
Fix available
A fix is available. Upgrade to 7.7.3 / 8.4.0 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit 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
Apache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter. A Velocity template can be provided through Velocity templates in a configset `velocity/` directory or as a parameter. A user defined configset could contain renderable, potentially malicious, templates. Parameter provided templates are disabled by default, but can be enabled by setting `params.resource.loader.enabled` by defining a response writer with that setting set to `true`. Defining a response writer requires configuration API access. Solr 8.4 removed the params resource loader entirely, and only enables the configset-provided template rendering when the configset is `trusted` (has been uploaded by an authenticated user).

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 versions 5.0.0 to 8.3.1 contain a Remote Code Execution vulnerability in the VelocityResponseWriter. Attackers with configset API access can inject malicious Velocity templates through either a configset's velocity/ directory or via request parameters when params.resource.loader.enabled is explicitly enabled. Successful exploitation allows arbitrary code execution on the server.

MitigationUpgrade to Apache Solr 8.4 or later, which removes the params resource loader and restricts configset template rendering to trusted (authenticated-uploaded) configsets only. Ensure unauthenticated configset uploads are not permitted.

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, < 7.7.3>= 8.0.0, < 8.4.0
Primavera UnifierApplication
Affected:>= 17.7, <= 17.12= 16.1= 16.2= 18.8= 19.12

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

CVSS:3.1/AV:N/AC:H/PR:L/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. Check installed Solr version
    Query the Solr admin API endpoint /solr/admin/info/system or run 'bin/solr version' to obtain the running Solr version number
    Affected if The version is >= 5.0.0 and < 7.7.3, or >= 8.0.0 and < 8.4.0
  2. Verify VelocityResponseWriter is in use
    Review solrconfig.xml files for <queryResponseWriter name="velocity" ...> configuration or check if velocity is explicitly configured as a response writer
    Affected if VelocityResponseWriter is configured as a response writer in any solrconfig.xml
  3. Check for params.resource.loader.enabled
    Search solrconfig.xml files for the parameter 'params.resource.loader.enabled' set to 'true', or inspect the runtime parameters being passed to Solr requests
    Affected if params.resource.loader.enabled is set to true in any configset configuration
  4. Inspect custom configsets for velocity templates
    Examine the conf/configsets directory or uploaded configset directories for the presence of a velocity/ subdirectory containing custom .vm template files
    Affected if A custom configset contains a velocity/ directory with user-defined Velocity templates
  5. Check for exposed configuration API
    Verify if the Solr Configuration API endpoint (/solr/admin/configs) is accessible without authentication or via an untrusted user
    Affected if The config API is accessible to untrusted users who can upload or modify configsets

You are affected if running a vulnerable Solr version AND either VelocityResponseWriter is enabled with params.resource.loader.enabled=true OR untrusted users can upload custom configsets with velocity templates.

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.4.0 or later
Fixed in 7.7.38.4.0
Vendor patch issues.apache.org →
Interim mitigation

Upgrade to Apache Solr 8.4 or later, which removes the params resource loader and restricts configset template rendering to trusted (authenticated-uploaded) configsets only. Ensure unauthenticated configset uploads are not permitted.

Recommended fix High confidence

Solr 7.7.3+ or 8.4.0+

  1. Upgrade Apache Solr to version 7.7.3 or later for the 7.x branch
  2. If using Solr 8.x, upgrade to version 8.4.0 or later
  3. After upgrading, verify that the VelocityResponseWriter is not enabled with untrusted configsets
  4. For Primavera Unifier, ensure the underlying Solr version is also updated to a fixed version
Caveat Solr 8.4 removed the params resource loader entirely; applications relying on this feature may need to be reconfigured to use trusted configsets

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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