Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1620351 - (CVE-2018-1999046) CVE-2018-1999046 jenkins: Unauthorized users could access agent logs
CVE-2018-1999046 jenkins: Unauthorized users could access agent logs
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180815,repor...
: Security
Depends On: 1620352
Blocks: 1620339
  Show dependency treegraph
 
Reported: 2018-08-23 00:42 EDT by Sam Fowler
Modified: 2018-10-31 03:02 EDT (History)
13 users (show)

See Also:
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:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sam Fowler 2018-08-23 00:42:51 EDT
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 00:43:12 EDT
Created jenkins tracking bugs for this issue:

Affects: fedora-all [bug 1620352]
Comment 3 Jason Shepherd 2018-10-31 02:59:45 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.