Jenkins 2.191 and earlier, LTS 2.176.2 and earlier allowed users to obtain CSRF tokens without an associated web session ID, resulting in CSRF tokens that did not expire and could be used to bypass CSRF protection for the anonymous user.
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Link | Tags |
---|---|
http://www.openwall.com/lists/oss-security/2019/08/28/4 | third party advisory mailing list |
https://access.redhat.com/errata/RHSA-2019:2789 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2019:3144 | third party advisory vendor advisory |
https://www.oracle.com/security-alerts/cpuapr2022.html | third party advisory patch |
https://jenkins.io/security/advisory/2019-08-28/#SECURITY-1491 | vendor advisory |