Loading vulnerability…
CVE-2019-12409 is a remote code execution vulnerability in Apache Solr versions 8.1.1 and 8.2.0 due to insecure default configuration of the ENABLE_REMOTE_JMX_OPTS option in solr.in.sh. By default, JMX monitoring is enabled and exposed on RMI_PORT (default 18983) without authentication. If this port is accessible, an attacker can connect to the JMX service and potentially upload and execute arbitrary code on the Solr server.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains 'MJET', a JMX exploitation toolkit targeting insecure Java Management Extensions (JMX) RMI endpoints, specifically exploiting CVE-2019-12409 in Apache Solr (and potentially other Java applications with exposed JMX). The main exploit script is 'mjet/mjet.py', written in Python for Jython, which provides a CLI to connect to a remote JMX RMI service, deploy a malicious MBean (written in Java), and interact with it. The toolkit supports multiple attack modes: installing/uninstalling the payload, executing arbitrary system commands, running JavaScript, changing the payload password, and exploiting Java deserialization vulnerabilities via ysoserial. It can also run a web server to serve the malicious payload JAR. The Java payload (MogwaiLabsPayload) provides methods for command execution, JavaScript execution, and password management. Example scripts in JavaScript are provided for further exploitation (e.g., loading Meterpreter). The exploit requires the target to have remote JMX enabled and accessible, and can be used to gain full remote code execution on the target system. The repository is well-documented, with detailed usage instructions and example attack scenarios.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.