cve.bz

CVE-2019-12409 apache solr

9.8 criticalExploit referenceEPSS 22%Fix available

Critical (9.8) in apache solr. EPSS 22% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.solr:solr-core 8.3.0.

On this page
The 8.1.1 and 8.2.0 releases of Apache Solr contain an insecure setting for the ENABLE_REMOTE_JMX_OPTS configuration option in the default solr.in.sh configuration file shipping with Solr. If you use the default solr.in.sh file from the affected releases, then JMX monitoring will be enabled and exposed on RMI_PORT (default=18983), without any authentication. If this port is opened for inbound traffic in your firewall, then anyone with network access to your Solr nodes will be able to access JMX, which may in turn allow them to upload malicious code for execution on the Solr server.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
22% (unchanged from 22% a week ago; 21% 30 days ago) estimated probability of exploitation activity in the next 30 days; 98th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-434 Unrestricted Upload of File with Dangerous Type
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • org.apache.solr:solr-core (Maven): fixed in 8.3.0

Ask an AI about this CVE

Show the promptExplain CVE-2019-12409 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-12409?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-12409?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-12409 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
apache:solr8.1.1
apache:solr8.2.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-2289-pqfq-6wx7Mavenorg.apache.solr:solr-core>=8.1.1 <8.3.08.3.0

Red Hat

Red Hat rates this Important.

Red Hat's mitigation

Per Solr guidance: "Make sure your effective solr.in.sh file has ENABLE_REMOTE_JMX_OPTS set to 'false' on every Solr node and then restart Solr. Note that the effective solr.in.sh file may reside in /etc/defaults/ or another location depending on the install. You can then validate that the 'com.sun.management.jmxremote*' family of properties are not listed in the "Java Properties" section of the Solr Admin UI, or configured in a secure way. There is no need to upgrade or update any code."

ProductPackageStateAdvisory
Red Hat JBoss Data Virtualization 6solr-coreNot affected
Red Hat JBoss Enterprise Application Platform 6solr-coreOut of support scope
Red Hat JBoss Fuse 6solr-coreNot affected
Red Hat JBoss Fuse Service Works 6solr-coreOut of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2019-12409.

Attack patterns (CAPEC)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON