Cross-project webhook token disclosure via ID-only lookup
Published Feb 28, 2022 · Updated Apr 23, 2025
Authorization bypass in Rundeck before 3.3.15 and 3.4.0 through 3.4.4 allows remote authenticated users to read other projects' webhooks. WebhookController.get authorizes the project named in the request but formerly fetched the webhook by numeric ID alone, without verifying that the record belonged to that project. Read permission for webhooks in any project is sufficient to expose another project's definitions and tokens, which can then trigger the associated webhooks.
Summary
What happened
Authorization bypass in Rundeck before 3.3.15 and 3.4.0 through 3.4.4 allows remote authenticated users to read other projects' webhooks. WebhookController.get authorizes the project named in the request but formerly fetched the webhook by numeric ID alone, without verifying that the record belonged to that project. Read permission for webhooks in any project is sufficient to expose another project's definitions and tokens, which can then trigger the associated webhooks.
The record
- CVE
- CVE-2021-41111
- Published
- Feb 28, 2022
- Updated
- Apr 23, 2025
- Vendor
- PagerDuty
- Product
- Rundeck
- Classifications
- CWE-639, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 28, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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=< 3.3.15
- Affected versionversion=>= 3.4.0, < 3.4.5
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.
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