CVE-2017-2611 Incorrect Authorization in Jenkins Core

Medium 4.3 Published Updated

Users with read access can trigger background cleanup processes, potentially causing excessive load and denial of service on Jenkins.

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-2611?

CVE-2017-2611 is a medium-severity missing authorization vulnerability in Jenkins Jenkins, published on 8 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Jenkins before versions 2.44, 2.32.2 is vulnerable to an insufficient permission check for periodic processes (SECURITY-389). The URLs /workspaceCleanup and /fingerprintCleanup did not perform permission checks, allowing users with read access to Jenkins to trigger these background processes (that are otherwise performed daily), possibly causing additional load on Jenkins master and agents.

Weakness: CWE-863, CWE-358

Which versions are affected by CVE-2017-2611?

2 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 versions2.44
org.jenkins-ci.main:jenkins-core MavenAll versions2.44

Products include Jenkins Jenkins, Redhat Openshift.

How do I fix CVE-2017-2611?

Upgrade org.jenkins-ci.main:jenkins-core to 2.44 or later.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2017-2611 being exploited?

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

All Jenkins Jenkins vulnerabilities

Sources

Also known as GHSA-3297-944x-j7x7.

Is CVE-2017-2611 in your software?

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

Check your SBOMs for free