Fedora Account System
Red Hat Associate
Red Hat Customer
A flaw was found in kubevirt/containerized-data-importer. A tenant who can create or update a VirtualMachine in their own namespace can set the cdi.kubevirt.io/storage.checkStaticVolume annotation on an embedded DataVolumeTemplate together with a cross-namespace clone source. The VM admission check (validateVirtualMachineDataVolumeTemplateNamespace) only validates the DataVolume's own namespace and does not restrict annotations or spec.source.pvc.namespace, so the request passes. The annotation is propagated onto the generated DataVolume, where AuthorizeSA treats it as noTokenOkay and converts a failed service-account clone-authorization SubjectAccessReview into an allowed result (ErrNoTokenOkay), which virt-controller accepts. virt-controller then creates the clone DataVolume on the tenant's behalf, and CDI - which proceeds with normal population when no statically provisioned PV is found - can clone the victim namespace's PVC into the attacker's namespace, resulting in cross-tenant data disclosure.