The Jenkins Credentials Plugin allowed the creation of Certificate credentials from a PKCS#12 file on the Jenkins master. Users with permission to create or update credentials could use the associated form validation to confirm the existence of files with an attacker-specified path. Additionally, they could create credentials from any valid PKCS#12 file on the Jenkins master. With the ability to configure jobs to access these credentials, they could obtain the certificate content. External References: https://jenkins.io/security/advisory/2019-05-21/#SECURITY-1322
"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." 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
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.1 Via RHSA-2019:1636 https://access.redhat.com/errata/RHSA-2019:1636
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2019-10320