Vulnerability Details : CVE-2016-0790

Jenkins before 1.650 and LTS before 1.642.2 do not use a constant-time algorithm to verify API tokens, which makes it easier for remote attackers to determine API tokens via a brute-force approach.
Published 2016-04-07 23:59:02
Updated 2018-01-05 02:30:30
Source Red Hat, Inc.
View at NVD,   CVE.org
Vulnerability category: Information leak

Threat overview for CVE-2016-0790

Top countries where our scanners detected CVE-2016-0790
Top open port discovered on systems with this issue 8088
IPs affected by CVE-2016-0790 1,862
Threat actors abusing to this issue? Yes
Find out if you* are affected by CVE-2016-0790!
*Directly or indirectly through your vendors, service providers and 3rd parties. Powered by attack surface intelligence from SecurityScorecard.

Exploit prediction scoring system (EPSS) score for CVE-2016-0790

Probability of exploitation activity in the next 30 days: 0.30%

Percentile, the proportion of vulnerabilities that are scored at or less: ~ 65 % EPSS Score History EPSS FAQ

CVSS scores for CVE-2016-0790

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source
5.0
 MEDIUM AV:N/AC:L/Au:N/C:P/I:N/A:N
10.0
2.9
 NIST
5.3
 MEDIUM CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
3.9
1.4
 NIST

CWE ids for CVE-2016-0790

References for CVE-2016-0790

Products affected by CVE-2016-0790

This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to CVEdetails.com terms of use!
Accept Close