CVE-2011-4642Not scoredCWE-352

CVE-2011-4642: Splunk vulnerability

Splunk

Affected: Splunk · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

28.6%probability of exploitation in the next 30 days

98th percentile

050100

Higher than 98% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Cross-Site Request Forgery
Vendor: Splunk
Published: January 2012
Band: Likely to be exploited (10% or more), January 2012

CoverageNo articles yet

No CyberSIXT article names CVE-2011-4642 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.