CVE-2017-1000399 Exposure of Sensitive Information to an Unauthorized Actor in Jenkins

Medium 4.3 Published Updated

Unauthenticated or low-privilege users can view details of restricted build queue items via the remote API, leaking sensitive job information.

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-2017-1000399?

CVE-2017-1000399 is a medium-severity vulnerability in Jenkins Jenkins, published on 26 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

The Jenkins 2.73.1 and earlier, 2.83 and earlier remote API at /queue/item/(ID)/api showed information about tasks in the queue (typically builds waiting to start). This included information about tasks that the current user otherwise has no access to, e.g. due to lack of Item/Read permission. This has been fixed, and the API endpoint is now only available for tasks that the current user has access to.

Weakness: CWE-200

Which versions are affected by CVE-2017-1000399?

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

PackageAffectedFixed in
org.jenkins-ci.main:jenkins-core MavenAll versions2.73.2
org.jenkins-ci.main:jenkins-core MavenAll versions2.73.2
org.jenkins-ci.main:jenkins-core MavenFrom 2.742.84
org.jenkins-ci.main:jenkins-core MavenFrom 2.742.84

Products include Jenkins Jenkins.

How do I fix CVE-2017-1000399?

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

Is CVE-2017-1000399 being exploited?

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

All Jenkins Jenkins vulnerabilities

Sources

Also known as GHSA-g78x-xmv8-23xp.

Is CVE-2017-1000399 in your software?

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

Check your SBOMs for free