Webhook signature recovery via timing side channel
Published Jul 27, 2022 · Updated Aug 3, 2024
Timing side channel in Jenkins GitHub Plugin 1.34.4 and earlier allows remote attackers to recover a valid webhook signature. The webhook validation routine compares the provided and computed signatures with a non-constant-time function, exposing match progress through response timing. Exploitation requires repeated network measurements against an endpoint configured with a webhook secret and yields a signature accepted as authentic.
Summary
What happened
Timing side channel in Jenkins GitHub Plugin 1.34.4 and earlier allows remote attackers to recover a valid webhook signature. The webhook validation routine compares the provided and computed signatures with a non-constant-time function, exposing match progress through response timing. Exploitation requires repeated network measurements against an endpoint configured with a webhook secret and yields a signature accepted as authentic.
The record
- CVE
- CVE-2022-36885
- Published
- Jul 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- GitHub Plugin
- Classifications
- CWE-208, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 27, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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.34.4
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