Cluster takeover via overprivileged service account token
Published Jul 25, 2024 · Updated Mar 13, 2025
Incorrect access control in Kuma 2.7.0 allows remote authenticated users to take over Kubernetes clusters via a stolen service account token. The Kubernetes deployment binds the kuma-control-plane service account to permissions that expose cluster Secrets, while its pod mounts the inherited credential. Exploitation requires control of a pod or worker node that can obtain the token; the token then permits Secret access and cluster-wide privilege escalation.
Summary
What happened
Incorrect access control in Kuma 2.7.0 allows remote authenticated users to take over Kubernetes clusters via a stolen service account token. The Kubernetes deployment binds the kuma-control-plane service account to permissions that expose cluster Secrets, while its pod mounts the inherited credential. Exploitation requires control of a pod or worker node that can obtain the token; the token then permits Secret access and cluster-wide privilege escalation.
The record
- CVE
- CVE-2024-36542
- Published
- Jul 25, 2024
- Updated
- Mar 13, 2025
- Vendor
- Kong Inc.
- Product
- Kuma
- Classifications
- CWE-277, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2024CVE publishedPublication date reported by the CVE source.
- Mar 13, 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=2.7.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.
Weakness, pattern, technique
Public exploit references
- k8s-rbac-pocproof of concept · unverified
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