Bug 1539480 – CVE-2017-1000503 jenkins: Race condition during startup can result in default security settings not being applied

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1539480 - (CVE-2017-1000503) CVE-2017-1000503 jenkins: Race condition during startup can result in default security settings not being applied

Summary:	CVE-2017-1000503 jenkins: Race condition during startup can result in default...

Status:	NEW

Aliases:	CVE-2017-1000503

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	high Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=important,public=20171214,repo...
Keywords:	Security

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-01-28 20:52 EST by Sam Fowler
Modified:	2018-06-29 18:31 EDT (History)
CC List:	9 users (show)

See Also:
Fixed In Version:	jenkins 2.95, jenkins-lts 2.89.2
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Sam Fowler 2018-01-28 20:52:27 EST

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.

External References:
https://nvd.nist.gov/vuln/detail/CVE-2017-1000503
https://jenkins.io/security/advisory/2017-12-14/

Note You need to log in before you can comment on or make changes to this bug.