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!

See your relevant APM services, dashboards, and alerts in one place with the updated ...

As a Splunk Observability user, you have a lot of data you have to manage, prioritize, and troubleshoot on a ...

Index This | What goes away as soon as you talk about it?

May 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this month’s ...

What's New in Splunk Observability Cloud and Splunk AppDynamics - May 2025

This month, we’re delivering several new innovations in Splunk Observability Cloud and Splunk AppDynamics ...