Vulnerability Description
Jenkins before 1.650 and LTS before 1.642.2 do not use a constant-time algorithm to verify CSRF tokens, which makes it easier for remote attackers to bypass a CSRF protection mechanism via a brute-force approach.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Redhat | Openshift | 3.1 |
| Jenkins | Jenkins | <= 1.649 |
Related Weaknesses (CWE)
References
- http://rhn.redhat.com/errata/RHSA-2016-1773.html
- https://access.redhat.com/errata/RHSA-2016:0711
- https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-2PatchVendor Advisory
- http://rhn.redhat.com/errata/RHSA-2016-1773.html
- https://access.redhat.com/errata/RHSA-2016:0711
- https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-2PatchVendor Advisory
FAQ
What is CVE-2016-0791?
CVE-2016-0791 is a vulnerability with a CVSS score of 9.8 (CRITICAL). Jenkins before 1.650 and LTS before 1.642.2 do not use a constant-time algorithm to verify CSRF tokens, which makes it easier for remote attackers to bypass a CSRF protection mechanism via a brute-for...
How severe is CVE-2016-0791?
CVE-2016-0791 has been rated CRITICAL with a CVSS base score of 9.8/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2016-0791?
Check the references section above for vendor advisories and patch information. Affected products include: Redhat Openshift, Jenkins Jenkins.