Jenkins 2.213 and earlier, LTS 2.204.1 and earlier improperly reuses encryption key parameters in the Inbound TCP Agent Protocol/3, allowing unauthorized attackers with knowledge of agent names to obtain the connection secrets for those agents, which can be used to connect to Jenkins, impersonating those agents. References: https://jenkins.io/security/advisory/2020-01-29/#SECURITY-1682 http://www.openwall.com/lists/oss-security/2020/01/29/1
Created jenkins tracking bugs for this issue: Affects: fedora-all [bug 1797081]
"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 bug has been fixed by https://errata.devel.redhat.com/advisory/50532 that brought Jenkins 2.204.2