cve/2023/CVE-2023-26484.md

18 lines
1.5 KiB
Markdown
Raw Normal View History

2024-06-07 17:53:02 +00:00
### [CVE-2023-26484](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-26484)
![](https://img.shields.io/static/v1?label=Product&message=kubevirt&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3D%20%3C%3D%200.59.0%20&color=brighgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-863%3A%20Incorrect%20Authorization&color=brighgreen)
### 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.
### POC
#### Reference
- https://github.com/kubevirt/kubevirt/issues/9109
#### Github
No PoCs found on GitHub currently.