Bug 1620351 (CVE-2018-1999046)

Summary: CVE-2018-1999046 jenkins: Unauthorized users could access agent logs
Product: [Other] Security Response Reporter: Sam Fowler <sfowler>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
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:39 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: 1620352    
Bug Blocks: 1620339    

Description Sam Fowler 2018-08-23 04:42:51 UTC 
Jenkins before LTS version 2.121.3 and weekly version 2.138 allow unauthorized users to access agent logs.

Users with Overall/Read permission were able to access the URL serving agent logs on the UI due to a lack of permission checks.

Access to the affected URL is now limited to users with the correct Agent/Connect permission.


External Reference:

https://jenkins.io/security/advisory/2018-08-15/#SECURITY-1071
Comment 1 Sam Fowler 2018-08-23 04:43:12 UTC 
Created jenkins tracking bugs for this issue:

Affects: fedora-all [bug 1620352]
Comment 2 Jason Shepherd 2018-10-30 05:22:20 UTC 
Upstream commit: https://github.com/jenkinsci/jenkins/commit/6867e4469525d16319b1bae9c840b933fe4e23c4
Comment 3 Jason Shepherd 2018-10-31 06:59:45 UTC 
By default Jenkins doesn't setup users without the Agent/Connect permission. It's possible to setup such users but it's best not to rely on Agent/Connect permission to prevent access to agent logs because of this issue on OpenShift Container Platform 3.10 and earlier.

Upgrade to OpenShift Container Platform 3.11 to pick up a fix for this issue.