CVE-2016-0791

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.

Category

9.8
CVSS
Severity: Critical
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.20%
Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory jenkins-ci.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://access.redhat.com/errata/RHSA-2016:0711 vendor advisory
http://rhn.redhat.com/errata/RHSA-2016-1773.html vendor advisory
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24 patch vendor advisory

Frequently Asked Questions

What is the severity of CVE-2016-0791?
CVE-2016-0791 has been scored as a critical severity vulnerability.
How to fix CVE-2016-0791?
To fix CVE-2016-0791, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2016-0791 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2016-0791 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.