Webhook token disclosure via non-constant-time comparison
Published Oct 25, 2023 · Updated Feb 13, 2025
Timing side channel in Jenkins Multibranch Scan Webhook Trigger Plugin 1.0.9 and earlier allows remote attackers to recover a webhook token. The webhook authentication path compares the supplied token with the configured token using a non-constant-time operation whose runtime leaks matching information. Repeated unauthenticated requests can reveal a valid token, which permits scans of matching multibranch jobs without other credentials.
Summary
What happened
Timing side channel in Jenkins Multibranch Scan Webhook Trigger Plugin 1.0.9 and earlier allows remote attackers to recover a webhook token. The webhook authentication path compares the supplied token with the configured token using a non-constant-time operation whose runtime leaks matching information. Repeated unauthenticated requests can reveal a valid token, which permits scans of matching multibranch jobs without other credentials.
The record
- CVE
- CVE-2023-46656
- Published
- Oct 25, 2023
- Updated
- Feb 13, 2025
- Vendor
- Jenkins Project
- Product
- Jenkins Multibranch Scan Webhook Trigger Plugin
- Classifications
- CWE-697
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 25, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=0 <=1.0.9
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.
Weakness, pattern, technique
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