Cluster takeover via overprivileged service account token
Published Jul 24, 2024 · Updated Aug 2, 2024
Incorrect authorization in FabEdge 0.8.1 and earlier allows attackers to read Kubernetes secrets using a stolen service account token. FabEdge pods expose a service account token whose RBAC permissions let its bearer list cluster-wide secrets through the Kubernetes API. Exploitation requires control of a worker node or another ability to place a FabEdge pod on an attacker-controlled node; the token can then support cluster takeover.
Summary
What happened
Incorrect authorization in FabEdge 0.8.1 and earlier allows attackers to read Kubernetes secrets using a stolen service account token. FabEdge pods expose a service account token whose RBAC permissions let its bearer list cluster-wide secrets through the Kubernetes API. Exploitation requires control of a worker node or another ability to place a FabEdge pod on an attacker-controlled node; the token can then support cluster takeover.
The record
- CVE
- CVE-2024-36536
- Published
- Jul 24, 2024
- Updated
- Aug 2, 2024
- Vendor
- FabEdge
- Product
- FabEdge
- Classifications
- CWE-863, T1552.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 24, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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 <=0.8.1
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
- k8s-rbac-pocproof of concept · demonstrated
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