Loading vulnerability…
Splunk Web in Splunk 4.2.x before 4.2.5 improperly restricts use of the mappy command when accessing Python classes. An authenticated administrator can leverage the Python sys module through a request to the search application to execute arbitrary code. The issue is identified as SPL-45172.
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 a single Metasploit module (modules/exploits/multi/http/splunk_mappy_exec.rb) that exploits a remote code execution vulnerability (CVE-2011-4642) in Splunk versions 4.2 to 4.2.4. The exploit targets the 'mappy' search command in the Splunk web interface, which allows authenticated admin users to execute arbitrary Python code. The module authenticates to the Splunk web interface (default port 8000) using provided or default credentials, then submits a specially crafted search query to the /en-US/api/search/jobs endpoint. This query leverages the vulnerable 'mappy' command to execute base64-encoded system commands on the server. The exploit works on both Windows and Linux/Unix platforms, running with SYSTEM or root privileges, respectively. The module is operational and provides remote command execution capabilities, but requires valid admin credentials to succeed. The only file in the repository is the Metasploit module itself, written in Ruby.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.