CVE-2016-0791
Jenkins CSRF Token Verification Timing Attack 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.
INFO
Published Date :
April 7, 2016, 11:59 p.m.
Last Modified :
Jan. 5, 2018, 2:30 a.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
5.9
Exploitability Score :
3.9
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2016-0791.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2016-0791 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2016-0791 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
Jan. 05, 2018
Action Type Old Value New Value Added Reference http://rhn.redhat.com/errata/RHSA-2016-1773.html [No Types Assigned] -
Modified Analysis by [email protected]
Jul. 14, 2016
Action Type Old Value New Value Changed CPE Configuration Configuration 1 OR *cpe:2.3:a:jenkins:jenkins:1.649:*:*:*:*:*:*:* (and previous) Configuration 2 OR *cpe:2.3:a:jenkins:jenkins:1.642.1:*:*:*:lts:*:*:* Configuration 1 OR *cpe:2.3:a:redhat:openshift:3.1:*:*:*:enterprise:*:*:* Configuration 2 OR *cpe:2.3:a:jenkins:jenkins:1.649:*:*:*:*:*:*:* (and previous) Configuration 3 OR *cpe:2.3:a:jenkins:jenkins:1.642.1:*:*:*:lts:*:*:* -
CVE Modified by [email protected]
Jul. 14, 2016
Action Type Old Value New Value Added Reference https://access.redhat.com/errata/RHSA-2016:0711 -
Modified Analysis by [email protected]
Jun. 14, 2016
Action Type Old Value New Value Changed CPE Configuration Configuration 1 OR *cpe:2.3:a:cloudbees:jenkins:1.649:*:*:*:*:*:*:* (and previous) *cpe:2.3:a:cloudbees:jenkins:1.642.1:*:lts:*:*:*:*:* (and previous) Configuration 1 OR *cpe:2.3:a:jenkins:jenkins:1.649:*:*:*:*:*:*:* (and previous) Configuration 2 OR *cpe:2.3:a:jenkins:jenkins:1.642.1:*:*:*:lts:*:*:* -
CVE Translated by [email protected]
Jun. 12, 2016
Action Type Old Value New Value Removed Translation CloudBees Jenkins en versiones anteriores a 1.650 y LTS en versiones anteriores a 1.642.2 no utiliza un algoritmo de tiempo constante para verificar tokens CSRF, lo que hace más fácil para atacantes remotos eludir el mecanismo de protección CSRF a través de una aproximación por fuerza bruta. Added Translation Jenkins en versiones anteriores a 1.650 y LTS en versiones anteriores a 1.642.2 no utiliza un algoritmo de tiempo constante para verificar tokens CSRF, lo que hace más fácil para atacantes remotos eludir el mecanismo de protección CSRF a través de una aproximación por fuerza bruta. -
CVE Modified by [email protected]
Jun. 11, 2016
Action Type Old Value New Value Changed Description CloudBees 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. 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. -
Modified Analysis by [email protected]
Apr. 11, 2016
Action Type Old Value New Value Added CPE Configuration Configuration 1 OR *cpe:2.3:a:cloudbees:jenkins:1.649:*:*:*:*:*:*:* (and previous) *cpe:2.3:a:cloudbees:jenkins:1.642.1:*:lts:*:*:*:*:* (and previous) Added CVSS V2 (AV:N/AC:L/Au:N/C:P/I:P/A:P) Added CVSS V3 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Changed Reference Type https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24 No Types Assigned https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24 Advisory, Patch Added CWE CWE-200 -
Initial Analysis by [email protected]
Apr. 08, 2016
Action Type Old Value New Value
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2016-0791 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2016-0791
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.72 }} 0.00%
score
0.77528
percentile