First published: Wed Jan 24 2018(Updated: )
A race condition during Jenkins 2.94 and earlier; 2.89.1 and earlier startup could result in the wrong order of execution of commands during initialization. There is a very short window of time after startup during which Jenkins may no longer show the 'Please wait while Jenkins is getting ready to work' message but Cross-Site Request Forgery (CSRF) protection may not yet be effective.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Jenkins Jenkins | <=2.89.1 | |
Jenkins Jenkins | <=2.94 | |
maven/org.jenkins-ci.main:jenkins-core | >=2.90<=2.94 | 2.95 |
maven/org.jenkins-ci.main:jenkins-core | >=2.81<=2.89.1 | 2.89.2 |
<=2.89.1 | ||
<=2.94 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-1000504 has been rated as a medium severity vulnerability.
To fix CVE-2017-1000504, upgrade Jenkins to version 2.95 or later.
CVE-2017-1000504 affects Jenkins versions 2.94 and earlier, as well as 2.89.1 and earlier.
CVE-2017-1000504 describes a race condition during the startup of Jenkins that could lead to improper command execution.
There are no recommended workarounds for CVE-2017-1000504; the best approach is to apply the patch by upgrading.