https://bugzilla.redhat.com/show_bug.cgi?id=1446122
Bug ID: 1446122
Summary: CVE-2017-1000354 jenkins: Login command allowed
impersonating any Jenkins user (SECURITY-466)
Product: Security Response
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: amaris(a)redhat.com
CC: abhgupta(a)redhat.com, bleanhar(a)redhat.com,
ccoleman(a)redhat.com, dedgar(a)redhat.com,
dmcphers(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
jgoulding(a)redhat.com, jkeck(a)redhat.com,
joelsmith(a)redhat.com, kseifried(a)redhat.com,
mizdebsk(a)redhat.com, msrb(a)redhat.com,
tdawson(a)redhat.com, tiwillia(a)redhat.com
The login command available in the remoting-based CLI stored the encrypted user
name of the successfully authenticated user in a cache file used to
authenticate further commands. Users with sufficient permission to create
secrets in Jenkins, and download their encrypted values (e.g. with
Job/Configure permission), were able to impersonate any other Jenkins user on
the same instance.
This has been fixed by storing the cached authentication as a hash-based MAC
with a key specific to the Jenkins instance and the CLI authentication cache.
Previously cached authentications are invalidated when upgrading Jenkins to a
version containing a fix for this.
Affected versions:
All Jenkins main line releases up to and including 2.56
All Jenkins LTS releases up to and including 2.46.1
Fixed in:
Jenkins main line users should update to 2.57
Jenkins LTS users should update to 2.46.2
External Reference:
https://jenkins.io/security/advisory/2017-04-26/#cli-login-command-allowe...
--
You are receiving this mail because:
You are on the CC list for the bug.