Approved changes feed: RSS · Atom

cpe:2.3:a:apache:solr:8.1.1:*:*:*:*:*:*:*

part: a version: 8.1.1 update: *

VendorApache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95)
ProductSolr (e541f611-5f4f-518b-9c5a-edac6afba2d9)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:apache/solr purl2cpe 2026-06-01 10:14:26.416769
pkg:github/apache/solr purl2cpe 2026-06-01 10:14:26.416770
pkg:maven/org.apache.solr/solr purl2cpe 2026-06-01 10:14:26.416772
pkg:maven/org.apache.solr/solrj purl2cpe 2026-06-01 10:14:26.416773
pkg:rpm/opensuse/solr purl2cpe 2026-06-01 10:14:26.416775
pkg:sourceforge/apache-solr purl2cpe 2026-06-01 10:14:26.416776

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2019-12409 vulnerable 2026-06-08 05:12:39.075328 Details available
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.
Published: 2019-11-18T20:50:59.000Z
Updated: 2024-08-04T23:17:39.994Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.