A race condition during Jenkins startup could result in the wrong order of execution of commands during initialization.
On Jenkins 2.81 and newer, including LTS 2.89.1, this could in rare cases (estimated less than 20% of new instances) result in failure to initialize the setup wizard on the first startup. This may result in the security settings not being set to their usual strict default
Created jenkins tracking bugs for this issue:
Affects: fedora-all [bug 1526592]
Affects: openshift-1 [bug 1526593]
The Openshift 3.7 Jenkins RPM is jenkins-0:2.73.3-1.el7.noarch, which contains jenkins.war (version 2.73.3). The spec file indicates that no modifications are applied to the war file.
According to the advisory, Jenkins 2.73.3 is not affected.