CVE-2017-2613: Cross-Site Request Forgery in Jenkins
Summary
CVE-2017-2613: Cross-Site Request Forgery 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 and offers a range of features for continuous integration and delivery. The vulnerable package in focus is 'org.jenkins-ci.main:jenkins-core', which is a core component of Jenkins responsible for its basic functionality.
Vulnerability Detail
The vulnerability identified as CVE-2017-2613 is a Cross-Site Request Forgery (CSRF) issue in Jenkins. Prior to versions 2.44 and 2.32.2, administrators could unknowingly create user records through a CSRF attack using GET requests. Although these user records were typically only retained until a system restart, malicious actors could manipulate administrators' web browsers to create a large number of user records. This vulnerability is tracked under the identifier SECURITY-406 and has a CVSS score of 5.4 (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L). The Common Weakness Enumeration (CWE) ID associated with this vulnerability is CWE-352.
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 temporary workaround, administrators can implement CSRF protection mechanisms in their Jenkins instances. This can be achieved by configuring Jenkins to require a 'crumb' token for all HTTP requests, which helps prevent CSRF attacks. The following code snippet demonstrates how to enable CSRF protection in Jenkins:
<jenkins.model.Jenkins>
<crumbIssuer class="hudson.security.csrf.DefaultCrumbIssuer">
<excludeClientIPFromCrumb>false</excludeClientIPFromCrumb>
</crumbIssuer>
</jenkins.model.Jenkins>
Please note that this workaround is not a permanent solution and should be used until the package is updated to a secure version.
Conclusion
In conclusion, the CVE-2017-2613 vulnerability in Jenkins exposes a Cross-Site Request Forgery (CSRF) issue that allows unauthorized creation of user records. It is crucial for Jenkins administrators to upgrade the 'org.jenkins-ci.main:jenkins-core' package to version 2.44 or higher to mitigate this vulnerability. Implementing CSRF protection mechanisms can serve as a temporary workaround until the package is updated. For further assistance and support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.main:jenkins-core →
FAQ
The vulnerability allows malicious actors to create user records in Jenkins instances through CSRF attacks. While the user records are typically temporary, they can still cause disruptions and potential security risks.
Jenkins instances running versions prior to 2.44 and 2.32.2 of the 'org.jenkins-ci.main:jenkins-core' package are affected by this vulnerability. Administrators with administrative privileges are particularly at risk.
At the time of this report, there are no known public exploits specifically targeting this vulnerability. However, it is essential to promptly address and patch the vulnerability to prevent potential exploitation.
While upgrading the 'org.jenkins-ci.main:jenkins-core' package is the recommended solution, administrators can implement CSRF protection mechanisms as a temporary workaround. This involves configuring Jenkins to require a 'crumb' token for all HTTP requests.
For more detailed information about this vulnerability, including its technical aspects and the fix, refer to the official GitHub advisory: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/05/GHSA-pwv6-872c-gcg6/GHSA-pwv6-872c-gcg6.json
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.main:jenkins-core.
