KubeVirt Isolation Detection Flaw Allows Arbitrary File Permission Changes
kubevirt
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| kubevirt.io/kubevirt Go |
|
|
kubevirt
| Product | Affected | Fixed in |
|---|---|---|
| kubevirt.io/kubevirt Go |
|
|
KubeVirt is a virtual machine management add-on for Kubernetes. In versions before 1.5.3 and 1.6.1, the virt-handler does not verify whether the launcher-sock is a symlink or a regular file. This oversight can be exploited, for example, to change the ownership of arbitrary files on the host node to the unprivileged user with UID 107 (the same user used by virt-launcher) thus, compromising the CIA (Confidentiality, Integrity and Availability) of data on the host. To successfully exploit this vulnerability, an attacker should be in control of the file system of the virt-launcher pod. This vulnerability is fixed in 1.5.3 and 1.6.1.
From the CVE record · GitHub_M
KubeVirt's virt-handler does not verify whether launcher-sock is a symlink or a regular file. An attacker who controls the virt-launcher pod's file system can exploit this to change ownership of arbitrary files on the host node to UID 107, potentially compromising host data.
Teams running the Go package kubevirt.io/kubevirt in versions before 1.5.3, from 1.6.0-alpha.0 to before 1.6.1, or from 1.6.0-alpha.0 to before 1.6.0-beta.0.0.20250801202148-3ce9f41c54d0 should check their deployments.