CVE-2017-1000503

Description

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.

Category

8.1
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 2.89% Top 15%
Vendor Advisory jenkins.io
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://jenkins.io/security/advisory/2017-12-14/ vendor advisory

Frequently Asked Questions

What is the severity of CVE-2017-1000503?
CVE-2017-1000503 has been scored as a high severity vulnerability.
How to fix CVE-2017-1000503?
To fix CVE-2017-1000503, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-1000503 being actively exploited in the wild?
It is possible that CVE-2017-1000503 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~3% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.