CVE-2011-4642 json
mappy.py in Splunk Web in Splunk 4.2.x before 4.2.5 does not properly restrict use of the mappy command to access Python classes, which all…
published 2012-01-03 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4560
- cvss
- 4.6
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 28.6%
- EPSS 28.6% chance of exploitation in 30 days, percentile 98%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
mappy.py in Splunk Web in Splunk 4.2.x before 4.2.5 does not properly restrict use of the mappy command to access Python classes, which allows remote authenticated administrators to execute arbitrary code by leveraging the sys module in a request to the search application, as demonstrated by a cross-site request forgery (CSRF) attack, aka SPL-45172.
Timeline
- First public exploit (Metasploit exploit/multi/http/splunk_mappy_exec)
- Published
Exploit prediction
28.62% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/multi/http/splunk_mappy_exec Splunk Search Remote Code Execution metasploit exploit, excellent rank, 2011-12-12
- EDB-18245 Splunk - Remote Command Execution remote, 2011-12-15
- sec-1.com http://www.sec-1.com/blog/?p=233 referenced PoC, tagged "exploit" by a source, unverified
- sec-1.com http://www.sec-1.com/blog/wp-content/uploads/2011/12/Attacking_Splunk_Release.pdf referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.6 | AV:N/AC:H/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
exploit-db.com
/exploits/18245/
exploit
-
sec-1.com
/blog/?p=233
exploit
-
sec-1.com
/blog/wp-content/uploads/2011/12/Attacking_Splunk_Release.pdf
exploit
-
splunk.com
/view/SP-CAAAGMM
vendor-advisory
-
securitytracker.com
/id?1026451
vdb-entry
-
secunia.com
/advisories/47232
third-party-advisory
Sources
- CVE List CVE-2011-4642
- NVD CVE-2011-4642
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.