CVE-2016-3721 Jenkins allows Remote Users to Inject Build Parameters

Medium 4.3 Published Updated

Authenticated users can inject build parameters into the environment, potentially leading to arbitrary code execution on the Jenkins server.

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-2016-3721?

CVE-2016-3721 is a medium-severity code injection vulnerability in Jenkins Jenkins, published on 17 May 2016. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Jenkins before 2.3 and LTS before 1.651.2 might allow remote authenticated users to inject arbitrary build parameters into the build environment via environment variables.

Weakness: CWE-17

Which versions are affected by CVE-2016-3721?

4 open source packages ship an affected version, including org.jenkins-ci.main:jenkins-core. It affects 2 products.

PackageAffectedFixed in
org.jenkins-ci.main:jenkins-core MavenAll versions1.651.2
org.jenkins-ci.main:jenkins-core MavenAll versions1.651.2
org.jenkins-ci.main:jenkins-core MavenFrom 1.6602.3
org.jenkins-ci.main:jenkins-core MavenFrom 1.6602.3

Products include Jenkins Jenkins, Redhat Openshift.

How do I fix CVE-2016-3721?

Upgrade org.jenkins-ci.main:jenkins-core to a fixed version for your release line: 1.651.2 or 2.3.

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

Is CVE-2016-3721 being exploited?

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

All Jenkins Jenkins vulnerabilities

Sources

Also known as GHSA-qf2h-h3xq-j93j.

Is CVE-2016-3721 in your software?

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

Check your SBOMs for free