Bug 1620337 (CVE-2018-1999042)

Summary: CVE-2018-1999042 jenkins: Deserialization of URL objects with host components
Product: [Other] Security Response Reporter: Sam Fowler <sfowler>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: ahardin, aos-bugs, bleanhar, bparees, ccoleman, dedgar, eparis, java-sig-commits, jgoulding, jokerman, mchappel, mizdebsk, msrb
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: jenkins 2.121.3, jenkins 2.138 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-10 10:36:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1620338    
Bug Blocks: 1620339    

Description Sam Fowler 2018-08-23 04:26:19 UTC 
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
Comment 1 Sam Fowler 2018-08-23 04:26:40 UTC 
Created jenkins tracking bugs for this issue:

Affects: fedora-all [bug 1620338]
Comment 2 Jason Shepherd 2018-10-30 05:15:34 UTC 
https://github.com/jenkinsci/jenkins/commit/727d58f690abf64f543407e1de3545eca76ad30e
Comment 4 Jason Shepherd 2018-10-30 23:25:04 UTC 
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