CVE-2019-10390 Jenkins Splunk Plugin Sandbox Bypass

High 8.8 Published Updated

Attackers with read permissions can execute arbitrary code on the Jenkins master via a Groovy script injection in the Splunk plugin.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2019-10390?

CVE-2019-10390 is a high-severity code injection vulnerability in Jenkins Splunk Plugin, published on 28 Aug 2019. Any signed-in user can exploit it over the network, with no action from the victim.

Official 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.

Which versions are affected by CVE-2019-10390?

2 open source packages ship an affected version, including com.splunk.splunkins:splunk-devops. It affects 1 product.

PackageAffectedFixed in
com.splunk.splunkins:splunk-devops MavenAll versions1.8.0
com.splunk.splunkins:splunk-devops MavenAll versions1.8.0

Products include Jenkins Splunk.

How do I fix CVE-2019-10390?

Upgrade com.splunk.splunkins:splunk-devops to 1.8.0 or later.

Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.

Is CVE-2019-10390 being exploited?

There is no known exploitation of CVE-2019-10390 in the wild and no public exploit code.

Sources

Also known as GHSA-cjr8-5rw4-wh65.

Is CVE-2019-10390 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free