CVE-2023-26484 On a compromised KubeVirt node, the virt-handler service account can be used to modify all node specs
- Published
- Updated
- Exploit status
- No public exploit known
Description
KubeVirt is a virtual machine management add-on for Kubernetes. In versions 0.59.0 and prior, if a malicious user has taken over a Kubernetes node where virt-handler (the KubeVirt node-daemon) is running, the virt-handler service account can be used to modify all node specs. This can be misused to lure-in system-level-privileged components which can, for instance, read all secrets on the cluster, or can exec into pods on other nodes. This way, a compromised node can be used to elevate privileges beyond the node until potentially having full privileged access to the whole cluster. The simplest way to exploit this, once a user could compromise a specific node, is to set with the virt-handler service account all other nodes to unschedulable and simply wait until system-critical components with high privileges appear on its node. No patches are available as of time of publication. As a workaround, gatekeeper users can add a webhook which will block the virt-handler service account to modify the spec of a node.
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| kubevirt.io/kubevirt(Go) | <= 0.59.0 | No fix listed |
| Microsoft azure linux | < 1.2.0-1 | 1.2.0-1 |
| Microsoft cbl mariner | < 0.59.0-20 | 0.59.0-20 |
| kubevirt github.com/kubevirt/kubevirt | = <= 0.59.0 | No fix listed |
| kubevirt github.com/kubevirt/kubevirt | <= 0.59.0 | No fix listed |
References
- https://github.com/kubevirt/kubevirt/security/advisories/GHSA-cp96-jpmq-xrr2 mitigation vendor-advisory
- kubevirt third-party-advisory vendor-advisory
- https://github.com/kubevirt/kubevirt/issues/9109 issue-tracking third-party-advisory
- github.com
- github.com product
- MSRC Security Update Guide vendor-advisory