First published: Wed Jan 24 2018(Updated: )
A race condition during Jenkins 2.81 through 2.94 (inclusive); 2.89.1 startup could result in the wrong order of execution of commands during initialization. This could in rare cases result in failure to initialize the setup wizard on the first startup. This resulted in multiple security-related settings not being set to their usual strict default.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Jenkins Jenkins | >=2.81<=2.94 | |
Jenkins Jenkins | =2.89.1 | |
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.81<=2.94 | ||
=2.89.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-1000503 is considered a medium severity vulnerability due to the potential for improper command execution during Jenkins startup.
To fix CVE-2017-1000503, upgrade Jenkins to version 2.95 or later, or to version 2.89.2 if using the LTS release.
CVE-2017-1000503 affects Jenkins versions 2.81 through 2.94 and version 2.89.1.
Failing to address CVE-2017-1000503 may lead to failure in initializing the setup wizard and potential security-related issues.
CVE-2017-1000503 was disclosed on December 14, 2017.