Unauthenticated build triggering via tokenless webhooks
Published Nov 15, 2022 · Updated Apr 30, 2025
Missing authentication in CloudBees Docker Hub/Registry Notification Plugin 2.6.2 and earlier allows remote attackers to trigger builds. The Docker Hub, Docker Registry 2.0, and Azure Container Registry webhook endpoints accept notifications without validating an API token. Network access to an exposed endpoint is sufficient to schedule jobs associated with an attacker-specified repository, consuming build resources and running configured build actions.
Summary
What happened
Missing authentication in CloudBees Docker Hub/Registry Notification Plugin 2.6.2 and earlier allows remote attackers to trigger builds. The Docker Hub, Docker Registry 2.0, and Azure Container Registry webhook endpoints accept notifications without validating an API token. Network access to an exposed endpoint is sufficient to schedule jobs associated with an attacker-specified repository, consuming build resources and running configured build actions.
The record
- CVE
- CVE-2022-45385
- Published
- Nov 15, 2022
- Updated
- Apr 30, 2025
- Vendor
- Jenkins Project
- Product
- CloudBees Docker Hub/Registry Notification
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 15, 2022CVE publishedPublication date reported by the CVE source.
- Apr 30, 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 <=2.6.2
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