First published: Wed Aug 28 2019(Updated: )
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.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.jenkins-ci.main:jenkins-core | >=2.177<=2.191 | 2.192 |
maven/org.jenkins-ci.main:jenkins-core | <=2.176.2 | 2.176.3 |
Jenkins | <=2.176.2 | |
Jenkins | <=2.191 | |
Oracle Communications Cloud Native Core Automated Test Suite | =1.9.0 | |
redhat openshift container platform | =3.11 | |
redhat openshift container platform | =4.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-10384 is a vulnerability in Jenkins where users can obtain CSRF tokens without an associated web session ID, allowing them to bypass CSRF protection.
CVE-2019-10384 has a severity rating of 8.8 (High).
To fix CVE-2019-10384, it is recommended to update Jenkins to version 2.191 or later, or LTS 2.176.3 or later.
You can find more information about CVE-2019-10384 on the following websites: [Openwall](http://www.openwall.com/lists/oss-security/2019/08/28/4), [Red Hat Errata 1](https://access.redhat.com/errata/RHSA-2019:2789), [Red Hat Errata 2](https://access.redhat.com/errata/RHSA-2019:3144).
The CWE (Common Weakness Enumeration) of CVE-2019-10384 is 352.