CSRF in Splunk
CVE-2011-4642
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.
Vulnerability class: CSRF (Cross-Site Request Forgery)
EPSS: 0.289 (98.0th percentile) — read the EPSS interpretation.
Affected products
- Splunk — versions 4.2, 4.2.1, 4.2.2
- N/a — versions n/a
Weakness classification (CWE)
Public proof-of-concept exploits
References
- cve@mitre.org (x_refsource_CONFIRM, Vendor Advisory)
- cve@mitre.org (vdb-entry, x_refsource_SECTRACK)
- cve@mitre.org (Exploit, x_refsource_MISC)
- cve@mitre.org (x_refsource_SECUNIA, third-party-advisory)
- cve@mitre.org (Exploit, x_refsource_MISC)
- cve@mitre.org (Exploit, exploit, x_refsource_EXPLOIT-DB)
Frequently asked questions
- What is CVE-2011-4642?
- CVE-2011-4642 is a vulnerability in Splunk, classified under Cross-Site Request Forgery (CSRF). Published 2012-01-03.
- Is CVE-2011-4642 known to be exploited?
- 2 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.