CVE-2016-0791: Infoleak
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.
Other sources
The following flaw was found in Jenkins:
The verification of user-provided CSRF crumbs with the expected value did not use a constant-time comparison algorithm, potentially allowing attackers to use statistical methods to determine valid CSRF crumbs using brute-force methods.
External References:
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24
— Red Hat
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2016-0791?
CVE-2016-0791 is considered a high-severity vulnerability due to its potential to allow remote attackers to bypass CSRF protection.
How do I fix CVE-2016-0791?
To fix CVE-2016-0791, upgrade Jenkins to version 1.650 or later, or to version 1.642.2 or later for LTS users.
What does CVE-2016-0791 affect?
CVE-2016-0791 affects Jenkins versions prior to 1.650 and LTS versions prior to 1.642.2.
How does CVE-2016-0791 exploit CSRF tokens?
CVE-2016-0791 exploits CSRF tokens by using a brute-force approach due to the lack of a constant-time algorithm for verification.
Is my Jenkins installation vulnerable to CVE-2016-0791?
If you are running Jenkins version before 1.650 or LTS version before 1.642.2, your installation is vulnerable to CVE-2016-0791.