Cluster privilege escalation via overprivileged operator role
Published Aug 20, 2024 · Updated Aug 21, 2024
Improper privilege management in Kanister before 0.112.0 allows remote authenticated users to gain cluster-level privileges. The default-kanister-operator deployment binds its service account to Kubernetes' edit ClusterRole, exposing DaemonSet writes, token creation, and account impersonation. Worker-node access to the operator is required; abuse grants control of privileged accounts and permits reading, modifying, or deleting cluster resources.
Summary
What happened
Improper privilege management in Kanister before 0.112.0 allows remote authenticated users to gain cluster-level privileges. The default-kanister-operator deployment binds its service account to Kubernetes' edit ClusterRole, exposing DaemonSet writes, token creation, and account impersonation. Worker-node access to the operator is required; abuse grants control of privileged accounts and permits reading, modifying, or deleting cluster resources.
The record
- CVE
- CVE-2024-43403
- Published
- Aug 20, 2024
- Updated
- Aug 21, 2024
- Vendor
- Kanister
- Product
- Kanister
- Classifications
- CWE-269, T1610
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 20, 2024CVE publishedPublication date reported by the CVE source.
- Aug 21, 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=0 <=*
- Affected versionversion=<= 0.110.0
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.
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