CVE-2016-0790

jenkins: Non-constant time comparison of API token (SECURITY-241)

Published Apr 7, 2016 CVSS 3.0 · 5.3 Medium EPSS 2.1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

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
Type Values Removed Values Added
Metrics epss

{'score': 0.00232}

epss

{'score': 0.00115}

Weaknesses

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Aug 5, 2024, 10:30 PM
Reserved
Dec 16, 2015, 12:00 AM
Status
Modified
Published
Apr 7, 2016, 11:59 PM
Modified
Jun 17, 2026, 12:38 AM
Severity
Important
Public date
Feb 24, 2016, 12:00 AM