Splunk Dev

Mitigation for CVE-2011-4642 Cross Site Scripting and Cross Site Request Forgery

Wilf
Explorer

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

Tags (2)
1 Solution

araitz
Splunk Employee
Splunk Employee

Yes, you can remove the files mappy.py and reducepy.py and remove or comment out their respective entries from commands.conf.

View solution in original post

0 Karma

araitz
Splunk Employee
Splunk Employee

Yes, you can remove the files mappy.py and reducepy.py and remove or comment out their respective entries from commands.conf.

0 Karma
Get Updates on the Splunk Community!

AppDynamics Summer Webinars

This summer, our mighty AppDynamics team is cooking up some delicious content on YouTube Live to satiate your ...

SOCin’ it to you at Splunk University

Splunk University is expanding its instructor-led learning portfolio with dedicated Security tracks at .conf25 ...

Credit Card Data Protection & PCI Compliance with Splunk Edge Processor

Organizations handling credit card transactions know that PCI DSS compliance is both critical and complex. The ...