CVE-2017-2604: Improper Authentication in Jenkins
Summary
CVE-2017-2604: Improper Authentication 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 is widely used in the software development industry for continuous integration and delivery. 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-2604 in Jenkins versions before 2.44 and 2.32.2 is related to improper authentication. It allowed low privilege users to act on administrative monitors without consistent protection from permission checks. This security flaw, known as SECURITY-371, could potentially enable unauthorized users to perform administrative actions and gain elevated privileges within the Jenkins environment. The vulnerability has a CVSS score of 4.3, indicating a moderate severity level.
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 affected administrative monitors by adjusting the permission settings within Jenkins. By carefully managing user privileges and permissions, the impact of this vulnerability can be mitigated. Here is an example of how to restrict access to the administrative monitors using the Jenkins Script Console:
import jenkins.model.Jenkins
def monitors = Jenkins.getInstance().administrativeMonitors
for (monitor in monitors) {
monitor.setRequiredPermission(hudson.model.Item.READ)
}
This script sets the required permission for all administrative monitors to 'READ', effectively limiting access to authorized users with the necessary privileges.
Conclusion
In conclusion, the vulnerability CVE-2017-2604 in Jenkins versions before 2.44 and 2.32.2 allows low privilege users to bypass authentication and act on administrative monitors. It is crucial to promptly upgrade Jenkins to the fixed versions and regularly update the software to mitigate security risks. 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 in software development.
The vulnerable package is 'org.jenkins-ci.main:jenkins-core', which is a core component of Jenkins responsible for its fundamental functionality.
This vulnerability allows low privilege users to act on administrative monitors, potentially gaining unauthorized access and elevated privileges within the Jenkins environment.
The CVSS score of this vulnerability is 4.3, indicating a moderate severity level.
To fix this vulnerability, upgrade Jenkins to version 2.44 or 2.32.2, depending on the currently installed version, by updating the 'org.jenkins-ci.main:jenkins-core' package.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.main:jenkins-core.
