CVE-2017-1000401: Improper Input Validation in Jenkins
Summary
CVE-2017-1000401: Improper Input Validation in Jenkins. Affects org.jenkins-ci.main:jenkins-core across 2 version ranges.
< 2.73.2
>= 2.74, < 2.84
Fixed in 2.73.2 or 2.84, 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 is widely used for continuous integration and delivery. The vulnerable package in question is 'org.jenkins-ci.main:jenkins-core'. This package is a core component of Jenkins and provides essential functionality for managing jobs, plugins, and user authentication.
Vulnerability Detail
The vulnerability, identified as CVE-2017-1000401, is an instance of improper input validation in Jenkins. Specifically, the default form control for passwords and other secrets, <f:password/>, in Jenkins versions 2.73.1 and earlier, as well as 2.83 and earlier, supports form validation via GET requests. This means that when form validation AJAX requests are made, secrets such as API keys could be logged to a HTTP access log in non-default configurations of Jenkins. This could potentially expose these secrets to users with access to these log files. The issue has been addressed in Jenkins versions 2.73.2 and 2.84, where form validation for <f:password/> is now always sent via POST, which is typically not logged.
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.73.22.73.2 -
>= 2.74, < 2.842.84
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 to the fixed versions is not immediately feasible, a workaround can be implemented by modifying the Jenkins configuration to disable access logging or restrict access to the log files. This can help mitigate the risk of exposing secrets to unauthorized users. However, it is important to note that this workaround is not a permanent solution and upgrading to the fixed versions is still recommended.
Conclusion
In conclusion, the vulnerability CVE-2017-1000401 in Jenkins exposes secrets to unauthorized users through the logging of form validation requests containing passwords and other secrets. Upgrading to the fixed versions or implementing the provided workaround can help mitigate this risk. For further support on 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 managing jobs, plugins, and user authentication.
The vulnerability could potentially expose secrets such as API keys to users with access to HTTP access logs in non-default configurations of Jenkins.
To fix this vulnerability, it is recommended to upgrade to Jenkins version 2.73.2 or later if using an affected version. Alternatively, you can implement the provided workaround by modifying the Jenkins configuration to disable access logging or restrict access to log files.
Yes, the CVSS score for this vulnerability is 2.2.
References
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.main:jenkins-core.
