Back to Database
Status published
Medium
CVE-2016-0790
Jenkins before 1.650 and LTS before 1.642.2 do not use...
Vulnerability Description
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.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
THREAT MONITOR
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2016-0790
Credits & Attribution
No credits recorded in the NVD database.
References
More from jenkins
View All →CVE-2019-1003010
A cross-site request forgery vulnerability exists in Jenkins Git Plugin...
Medium
4.3
CVE-2018-8718
Cross-site request forgery (CSRF) vulnerability in the Mailer Plugin 1.20...
High
8
CVE-2018-6356
Jenkins before 2.107 and Jenkins LTS before 2.89.4 did not...
Medium
6.5
CVE-2018-1999047
A improper authorization vulnerability exists in Jenkins 2.137 and earlier,...
Medium
6.5
CVE-2018-1999046
A exposure of sensitive information vulnerability exists in Jenkins 2.137...
Medium
4.3
Affected Vendor
jenkins
View all reports →Affected Software
jenkins, openshift
Vulnerable Versions:
0, 3.1
Timeline
Official Publish:
April 7th, 2016
Last Modified:
August 5th, 2024
Added to House:
July 20th, 2026
CVSS Vectors
V3:
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weaknesses (CWE)
No CWE data available
MITRE ATT&CK TTPs
No associated TTPs found for this vulnerability.