CVE-2016-0790 — Sensitive Information Exposure in Jenkins

CWE-200 — Sensitive Information ExposureCWE-2548 documents7 sources
Severity
5.3MEDIUMNVD
EPSS
0.2%
top 56.18%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
2
JenkinsRedhat Openshift
Timeline
PublishedApr 7
Latest updateMay 14

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.

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitability: 3.9 | Impact: 1.4

Affected Packages2 packages

▶NVDjenkins/jenkins1.642.1+1

Patches

Patch: wiki.jenkins-ci.org ↗Patch: wiki.jenkins-ci.org ↗

🔴Vulnerability Details

3
GHSA
Exposure of Sensitive Information in Jenkins Core↗2022-05-14
▶
OSV
Exposure of Sensitive Information in Jenkins Core↗2022-05-14
▶
CVEList
CVE-2016-0790: Jenkins before 1↗2016-04-07
▶

📋Vendor Advisories

2
Red Hat
jenkins: Non-constant time comparison of API token (SECURITY-241)↗2016-02-24
▶
Jenkins
Jenkins Security Advisory 2016-02-24↗2016-02-24
▶

💬Community

2
Bugzilla
CVE-2016-0788 CVE-2016-0789 CVE-2016-0790 CVE-2016-0791 CVE-2016-0792 jenkins: security advisory 2016-02-24 [fedora-all]↗2016-02-25
▶
Bugzilla
CVE-2016-0790 jenkins: Non-constant time comparison of API token (SECURITY-241)↗2016-02-25
▶
CVE-2016-0790 — Sensitive Information Exposure | cvebase