Skip to main content
CISA Known Exploited Vulnerabilities

Apache Solr VelocityResponseWriter Plug-In Remote Code Execution Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.

Added to KEV
2021-11-03
Remediation due
2022-05-03

Required action
Apply updates per vendor instructions.

CISA notes
https://nvd.nist.gov/vuln/detail/CVE-2019-17558

Description

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).

Key Findings

as of 2026-11-22
All KEV statistics→
  • CISA added CVE-2019-17558 to the KEV catalog 674 days after its CVE record was published.
  • It is one of 43 Apache entries in the CISA KEV catalog, and one of 12 added in 2021.
  • Its current EPSS score (98.6%) is higher than that of 85% of CISA KEV entries.

Severity

CVSS 3.1 · CISA · Base score7.5 HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HOpen in CVSS calculator
SSVC · CISA-ADP
Exploitationactive
Automatableno
Technical impacttotal

Remediation Timeline

BOD 26-04, US federal agencies
Publicly exposed asset
3 days
and forensic triage
Asset not publicly exposed
14 days
KEV due date
2022-05-03
181 days after listing

Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact total, 2025-02-06).

How the timeline is set

Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.

Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.

CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.

Affected Products

ProductAffected versions
Apache Solr
Apache Solr 5.0.0 to Apache Solr 8.3.1

References

29 links

Mailing lists

Other references

Record Details

Published
2019-12-30
Last updated
2025-10-21
Assigner (CNA)
apache
Credited to
-

More from Apache

All Apache CVEs→

CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.