CVE-2017-1000356: Cross-Site Request Forgery in Jenkins
Summary
CVE-2017-1000356: Cross-Site Request Forgery in Jenkins. Affects org.jenkins-ci.main:jenkins-core across 2 version ranges.
< 2.46.2
>= 2.50, < 2.57
Fixed in 2.46.2 or 2.57, 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 helps automate various tasks in software development. It provides a wide range of features and plugins to support continuous integration and delivery. The vulnerable package in focus is 'org.jenkins-ci.main:jenkins-core'.
Vulnerability Detail
The Jenkins versions 2.56 and earlier, as well as 2.46.1 LTS and earlier, are susceptible to a Cross-Site Request Forgery (CSRF) vulnerability in the Jenkins user database authentication realm. This vulnerability allows an attacker to create an account if signup is enabled or create an account if the victim is an administrator. In the latter case, the existing default admin user may be deleted, leading to various potential impacts. The vulnerability is assigned the CVE identifier CVE-2017-1000356 and has a CVSS score of 8.8.
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.46.22.46.2 -
>= 2.50, < 2.572.57
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
If upgrading Jenkins is not immediately feasible, a temporary workaround is to disable user signup or restrict user account creation to trusted individuals only. This can be achieved by modifying the Jenkins configuration settings. Here is an example of how to disable user signup by adding the following line to the Jenkins configuration file:
<disableSignup>true</disableSignup>
Conclusion
In conclusion, the Jenkins versions 2.56 and earlier, as well as 2.46.1 LTS and earlier, are vulnerable to a CSRF vulnerability that can lead to unauthorized account creation and potential impacts. It is crucial to upgrade Jenkins to the recommended versions or apply the provided workaround to mitigate the vulnerability. For further assistance and support in vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for org.jenkins-ci.main:jenkins-core →
FAQ
Jenkins is an open-source automation server that helps automate various tasks in software development. It is widely used for continuous integration and delivery.
Cross-Site Request Forgery (CSRF) is a type of security vulnerability where an attacker tricks a victim into performing unwanted actions on a web application in which the victim is authenticated.
The impacts of this vulnerability can vary depending on the actions performed by the attacker. Possible consequences include unauthorized access, privilege escalation, and data manipulation.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your Jenkins installation is affected by this vulnerability. Simply provide your pom.xml file, and Vulert will analyze it for open-source vulnerabilities in real-time.
For more detailed information about this vulnerability, you can refer to the GitHub Advisory Database entry: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/05/GHSA-85wq-pqhp-hmq6/GHSA-85wq-pqhp-hmq6.json
References
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.main:jenkins-core.
