Cluster takeover via overprivileged operator service account
Published May 2, 2024 · Updated Aug 2, 2024
Privilege escalation in KubeVirt 1.2.0 and earlier allows local users to take over a cluster using an operator service-account token. The kubevirt-operator ClusterRole grants cluster-wide secret and workload powers, while its pod-mounted token exposes those powers to anyone who obtains it. Exploitation requires prior access to the operator pod, a cluster node, or the token; the token then permits secret theft and privileged workload creation.
Summary
What happened
Privilege escalation in KubeVirt 1.2.0 and earlier allows local users to take over a cluster using an operator service-account token. The kubevirt-operator ClusterRole grants cluster-wide secret and workload powers, while its pod-mounted token exposes those powers to anyone who obtains it. Exploitation requires prior access to the operator pod, a cluster node, or the token; the token then permits secret theft and privileged workload creation.
The record
- CVE
- CVE-2024-33394
- Published
- May 2, 2024
- Updated
- Aug 2, 2024
- Vendor
- KubeVirt
- Product
- KubeVirt
- Classifications
- CWE-94, T1610
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 2, 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=-
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