KubeVirt Isolation Detection Flaw Allows Arbitrary File Permission Changes
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.5.3, 1.6.1, 1.6.0-beta.0.0.20250801202148-3ce9f41c54d0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- kubevirt kubevirt
fixed in 1.5.3; From 1.6.0-alpha.0 · fixed in 1.6.1
- kubevirt.io/kubevirtGo
fixed in 1.5.3
- kubevirt.io/kubevirtGo
From 1.6.0-alpha.0 · fixed in 1.6.1
- kubevirt.io/kubevirtGo
fixed in 1.5.3; From 1.6.0-alpha.0 · fixed in 1.6.0-beta.0.0.20250801202148-3ce9f41c54d0