Webhook token disclosure via timing discrepancy
Published Oct 19, 2022 · Updated May 8, 2025
Timing discrepancy in Jenkins Generic Webhook Trigger Plugin 1.84.1 and earlier allows remote attackers to recover webhook tokens. The token-validation path compares provided and expected webhook tokens with a non-constant-time operation, exposing measurable response-time differences. Repeated unauthenticated webhook requests and statistical analysis are required; a recovered token can authenticate webhook-trigger requests.
Summary
What happened
Timing discrepancy in Jenkins Generic Webhook Trigger Plugin 1.84.1 and earlier allows remote attackers to recover webhook tokens. The token-validation path compares provided and expected webhook tokens with a non-constant-time operation, exposing measurable response-time differences. Repeated unauthenticated webhook requests and statistical analysis are required; a recovered token can authenticate webhook-trigger requests.
The record
- CVE
- CVE-2022-43412
- Published
- Oct 19, 2022
- Updated
- May 8, 2025
- Vendor
- Jenkins Project
- Product
- Generic Webhook Trigger Plugin
- Classifications
- CWE-203, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 19, 2022CVE publishedPublication date reported by the CVE source.
- May 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=1.84.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo