Unauthenticated pipeline execution via wildcard permission match
Published Jan 4, 2022 · Updated Apr 23, 2025
Missing authentication in Spinnaker before 1.25.8 and 1.26.0 through 1.26.6 allows remote attackers to create and execute pipelines. Gate's favorite-icon permission rule performs an incorrect wildcard match, leaving pipeline creation and execution API requests authorized without credentials. Exposure of the Gate endpoint is sufficient when RBAC is not configured across every account and application, enabling deployment access and command execution against connected resources.
Summary
What happened
Missing authentication in Spinnaker before 1.25.8 and 1.26.0 through 1.26.6 allows remote attackers to create and execute pipelines. Gate's favorite-icon permission rule performs an incorrect wildcard match, leaving pipeline creation and execution API requests authorized without credentials. Exposure of the Gate endpoint is sufficient when RBAC is not configured across every account and application, enabling deployment access and command execution against connected resources.
The record
- CVE
- CVE-2021-43832
- Published
- Jan 4, 2022
- Updated
- Apr 23, 2025
- Vendor
- Spinnaker
- Product
- Spinnaker
- Classifications
- CWE-284, CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 4, 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=< 1.25.8
- Affected versionversion=>= 1.26.0, < 1.26.7
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