- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wilf
Explorer
01-09-2012
05:23 AM
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.
Can version 4.2.3 of splunk be locked down in any way to mitigate against this?
. Wilf
1 Solution
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
araitz

Splunk Employee
01-09-2012
08:13 AM
Yes, you can remove the files mappy.py and reducepy.py and remove or comment out their respective entries from commands.conf.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
araitz

Splunk Employee
01-09-2012
08:13 AM
Yes, you can remove the files mappy.py and reducepy.py and remove or comment out their respective entries from commands.conf.
