Developing for Splunk Platform

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!

Improve Your Security Posture

Watch NowImprove Your Security PostureCustomers are at the center of everything we do at Splunk and security ...

Maximize the Value from Microsoft Defender with Splunk

 Watch NowJoin Splunk and Sens Consulting for this Security Edition Tech TalkWho should attend:  Security ...

This Week's Community Digest - Splunk Community Happenings [6.27.22]

Get the latest news and updates from the Splunk Community here! News From Splunk Answers ✍️ Splunk Answers is ...