https://bugzilla.redhat.com/show_bug.cgi?id=1418731
Bug ID: 1418731
Summary: CVE-2017-2613 jenkins: User creation CSRF using GET by
admins (SECURITY-406)
Product: Security Response
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: anemec(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 following flaw was found in Jenkins:
When administrators accessed a URL like /user/example via HTTP GET, a user with
the ID example was created if it did not exist. While this user record was only
retained until restart in most cases, administrators' web browsers could be
manipulated to create a large number of user records.
Accessing these URLs now no longer results in a user record getting created,
Jenkins will respond with 404 Not Found if no such user exists. When using the
internal Jenkins user database, new users can be created via Manage Jenkins »
Manage Users. To restore the previous (unsafe) behavior, set the system
property hudson.model.User.allowUserCreationViaUrl to true as described on
Features controlled by system properties.
External References:
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+20...
Upstream patch:
https://github.com/jenkinsci/jenkins/commit/b88b20ec473200db35d0a0d29dcf1...
--
You are receiving this mail because:
You are on the CC list for the bug.