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.

Vulnerability/
CVE-2016-0791

critical

9.8

CWE

200 352

25/2/2016

7/4/2016

5/8/2024

CVE-2016-0791: Infoleak

First published: Thu Feb 25 2016(Updated: )

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.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
redhat/Jenkins	<1.650	1.650
redhat/Jenkins	<1.642.2	1.642.2
Red Hat OpenShift	=3.1
Jenkins LTS	<=1.649
Jenkins LTS	=1.642.1

Remedy

https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24

Never miss a vulnerability like this again

Reference Links

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.

agent/type
agent/first-publish-date
agent/weakness
agent/remedy
agent/severity
agent/author
agent/references
agent/description
collector/redhat-bugzilla
source/Red Hat
alias/CVE-2016-0791
agent/software-canonical-lookup
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/source
agent/tags
agent/softwarecombine
collector/nvd-index
agent/software-canonical-lookup-request
package-manager/redhat
vendor/redhat
canonical/red hat openshift
version/red hat openshift/3.1
vendor/jenkins
canonical/jenkins lts
version/jenkins lts/1.649
version/jenkins lts/1.642.1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.