The fix for SECURITY-901/CVE-2019-1003004 in Jenkins 2.150.2 and 2.160 did not reject existing remoting-based CLI authentication caches. This means that users who cached their CLI authentication before Jenkins was updated to 2.150.2 and newer, or 2.160 and newer, would remain authenticated. Support for the remoting-based CLI was dropped in Jenkins 2.165, so newer weekly releases are not affected. Jenkins 2.164.2 no longer supports legacy CLI authentication caches from before 2.150.2/2.160, and these users will be considered logged out. External References: https://jenkins.io/security/advisory/2019-04-10/#SECURITY-1289
Created jenkins tracking bugs for this issue: Affects: fedora-all [bug 1699702]
OpenShift Jenkins update policy[0]: "Any security advisory related updates to Jenkins core or the plugins we include in the OpenShift Jenkins master image will only occur in the v3.11 and v4.x branches of this repository. We do support running the v3.11 version of the master image against older v3.x (as far back as v3.4) OpenShift clusters if you want to pick up Jenkins security advisory updates." [0] https://github.com/openshift/jenkins/blob/master/README.md#jenkins-security-advisories-the-master-image-from-this-repository-and-the-oc-binary
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 3.11 Via RHBA-2019:1605 https://access.redhat.com/errata/RHBA-2019:1605