First published: Tue Jan 03 2012(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Splunk Splunk | =4.2.3 | |
Splunk Splunk | =4.2.2 | |
Splunk Splunk | =4.2 | |
Splunk Splunk | =4.2.4 | |
Splunk Splunk | =4.2.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2011-4642 has a high severity due to the potential for remote code execution.
To fix CVE-2011-4642, upgrade Splunk to version 4.2.5 or later.
CVE-2011-4642 affects Splunk versions 4.2.0 to 4.2.4.
Remote authenticated administrators can exploit CVE-2011-4642 to execute arbitrary code.
The vulnerability in CVE-2011-4642 is found in the mappy.py component of Splunk Web.