Jenkins before LTS version 2.121.3 and weekly version 2.138 allow deserialization of URL objects via Remoting (agent communication) and XStream. This could in rare cases be used by attackers to have Jenkins look up specified hosts' DNS records. External Reference: https://jenkins.io/security/advisory/2018-08-15/#SECURITY-637
Created jenkins tracking bugs for this issue: Affects: fedora-all [bug 1620338]
https://github.com/jenkinsci/jenkins/commit/727d58f690abf64f543407e1de3545eca76ad30e
The communication between Jenkins master and slave happens using the encrypted Jenkins Remoting JNLP4 protocol, [1]. Also the master exposes the JNLP port as a service, not a route. So it should not be accessible outside of the project unless the ovs-subnet plugin is in use. Because of these reasons the impact of the flaw itself if 'Low', Product Security have decided not to fix this issue in OCP 3.10 and earlier. Upgrade to OCP 3.11 to obtain a fix for this issue. [1] https://github.com/jenkinsci/remoting/blob/master/docs/protocols.md#jnlp4-connect