CVE-2019-10390

Description

A sandbox bypass vulnerability in Jenkins Splunk Plugin 1.7.4 and earlier allowed attackers with Overall/Read permission to provide a Groovy script to an HTTP endpoint that can result in arbitrary code execution on the Jenkins master JVM.

8.8

CVSS

Severity: High

CVSS 3.1 •

CVSS 2.0 •

EPSS 0.05%

Vendor Advisory jenkins.io

Affected: Jenkins project Jenkins Splunk Plugin

References

Link	Tags
http://www.openwall.com/lists/oss-security/2019/08/28/4	third party advisory mailing list
https://jenkins.io/security/advisory/2019-08-28/#SECURITY-1294	vendor advisory

Frequently Asked Questions

What is the severity of CVE-2019-10390?: CVE-2019-10390 has been scored as a high severity vulnerability.
How to fix CVE-2019-10390?: To fix CVE-2019-10390, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2019-10390 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2019-10390 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2019-10390?: CVE-2019-10390 affects Jenkins project Jenkins Splunk Plugin.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.