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.
Published: 2016-04-07
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
EUVD EUVD EUVD-2022-4363 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.
Github GHSA Github GHSA GHSA-jgpr-qrw2-6gp3 Exposure of Sensitive Information in Jenkins Core
History

Sun, 13 Jul 2025 13:45:00 +0000

Type Values Removed Values Added
Metrics epss

{'score': 0.00232}

epss

{'score': 0.00115}


cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2024-08-05T22:30:05.130Z

Reserved: 2015-12-16T00:00:00.000Z

Link: CVE-2016-0790

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2016-04-07T23:59:01.927

Modified: 2026-05-06T22:30:45.220

Link: CVE-2016-0790

cve-icon Redhat

Severity : Important

Publid Date: 2016-02-24T00:00:00Z

Links: CVE-2016-0790 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses