Unauthorized resource modification via wildcard API groups
Published Jul 15, 2021 · Updated Sep 16, 2024
Incorrect RBAC permissions in Rancher 2.0.0 through 2.4.15 and 2.5.0 through 2.5.8 allow remote authenticated users to modify protected resources. Rancher creates Kubernetes RBAC rules without the intended API-group restriction, turning access to a named resource in one group into access across matching resource names in other groups. Any cluster user holding the affected grant can reach management or downstream-cluster objects outside the intended authorization boundary, including secrets and cluster-level resources.
Summary
What happened
Incorrect RBAC permissions in Rancher 2.0.0 through 2.4.15 and 2.5.0 through 2.5.8 allow remote authenticated users to modify protected resources. Rancher creates Kubernetes RBAC rules without the intended API-group restriction, turning access to a named resource in one group into access across matching resource names in other groups. Any cluster user holding the affected grant can reach management or downstream-cluster objects outside the intended authorization boundary, including secrets and cluster-level resources.
The record
- CVE
- CVE-2021-25318
- Published
- Jul 15, 2021
- Updated
- Sep 16, 2024
- Vendor
- Rancher
- Product
- Rancher
- Classifications
- CWE-732, T1548
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 15, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=Rancher <2.4.16
- Affected versionversion=Rancher <2.5.9
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