Description
Jenkins before 1.650 and LTS before 1.642.2 do not use a constant-time algorithm to verify CSRF tokens, which makes it easier for remote attackers to bypass a CSRF protection mechanism via a brute-force approach.
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-2022-4403 | Jenkins before 1.650 and LTS before 1.642.2 do not use a constant-time algorithm to verify CSRF tokens, which makes it easier for remote attackers to bypass a CSRF protection mechanism via a brute-force approach. |
Github GHSA |
GHSA-jmw7-ph6p-33cc | Exposure of Sensitive Information in Jenkins Core |
References
History
Sun, 13 Jul 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2024-08-05T22:30:05.037Z
Reserved: 2015-12-16T00:00:00.000Z
Link: CVE-2016-0791
No data.
Status : Modified
Published: 2016-04-07T23:59:02.863
Modified: 2026-05-06T22:30:45.220
Link: CVE-2016-0791
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA