Webhook token disclosure via non-constant-time comparison
Published Oct 19, 2022 · Updated May 8, 2025
Timing side channel in Jenkins GitLab Plugin 1.5.35 and earlier allows remote attackers to derive a valid webhook token. The webhook validation path compares the supplied X-Gitlab-Token value with the configured job token using a non-constant-time operation. The attacker needs repeated network access to a token-protected /project webhook; a recovered token permits requests that can trigger the configured Jenkins job.
Summary
What happened
Timing side channel in Jenkins GitLab Plugin 1.5.35 and earlier allows remote attackers to derive a valid webhook token. The webhook validation path compares the supplied X-Gitlab-Token value with the configured job token using a non-constant-time operation. The attacker needs repeated network access to a token-protected /project webhook; a recovered token permits requests that can trigger the configured Jenkins job.
The record
- CVE
- CVE-2022-43411
- Published
- Oct 19, 2022
- Updated
- May 8, 2025
- Vendor
- Jenkins Project
- Product
- GitLab 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.5.35
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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