CVE-2017-2606: Information Exposure in Jenkins
Summary
CVE-2017-2606: Exposure of Sensitive Information to an Unauthorized Actor in Jenkins. Affects org.jenkins-ci.main:jenkins-core across 2 version ranges.
< 2.32.2
>= 2.34, < 2.44
Fixed in 2.32.2 or 2.44, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Jenkins is an open-source automation server that enables developers to build, test, and deploy their software projects. It provides a wide range of plugins and integrations to support continuous integration and delivery processes. The vulnerable package in question is 'org.jenkins-ci.main:jenkins-core', which is a core component of Jenkins responsible for its fundamental functionality.
Vulnerability Detail
The vulnerability, identified as CVE-2017-2606, involves an information exposure in the internal API of Jenkins. It allows unauthorized access to item names that should not be visible. This vulnerability affects Jenkins versions before 2.44 and 2.32.2. While authenticated users with appropriate access are not impacted, anonymous users can exploit this vulnerability to obtain a list of items via an UnprotectedRootAction. The impact of this vulnerability is considered moderate, with a CVSS score of 4.3.
How To Fix
Latest published version: 2.587 as of 22 Oct 2026
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 2.32.22.32.2 -
>= 2.34, < 2.442.44
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a workaround, administrators can restrict access to the UnprotectedRootAction API by configuring appropriate network or firewall rules. This can help mitigate the risk of unauthorized access to item names. However, applying the recommended fix by upgrading to the latest version is the most effective solution.
Conclusion
In conclusion, the CVE-2017-2606 vulnerability in Jenkins exposes sensitive information to unauthorized actors. It affects anonymous users of Jenkins versions before 2.44 and 2.32.2. To mitigate this vulnerability, it is crucial to upgrade Jenkins to the recommended versions and review access controls. For further assistance and support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.main:jenkins-core →
FAQ
Jenkins is an open-source automation server used for continuous integration and delivery of software projects.
The vulnerable package is 'org.jenkins-ci.main:jenkins-core', which is a core component of Jenkins responsible for its fundamental functionality.
Anonymous users of Jenkins versions before 2.44 and 2.32.2 are affected by this vulnerability. Authenticated users with appropriate access are not impacted.
The impact of this vulnerability is considered moderate. It allows unauthorized access to item names that should not be visible.
To fix this vulnerability, it is recommended to upgrade Jenkins to version 2.44 or 2.32.2. Additionally, review and adjust access controls and permissions to restrict unauthorized access.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.main:jenkins-core.
