kubevirt/virt-cdi-importer [1] v1.4.0 to v1.5.3 inclusive were reported to be disabling TLS certificate validation when importing data into PVCs from container registries. This could enable man-in-the-middle attacks between a container registry and the virt-cdi-component, leading to possible undetected tampering of trusted container image content. [1] https://github.com/kubevirt/containerized-data-importer
Statement: No public release of Red Hat Container Native Virtualization is affected by this flaw.
UNCONFIRMED: To configure /etc/containers/policy.json to validate GPG signed container images where possible, see [1]. For information about integrating container image signing into container publishing workflow, see [2]. [1] https://github.com/containers/image/blob/f0cbc16b444d729362c78244c715b45bf4019b71/docs/containers-policy.json.md [2] https://access.redhat.com/articles/2750891
External References: https://github.com/kubevirt/containerized-data-importer/issues/678
Mitigation: The vulnerability can only be triggered by an authenticated kubernetes user who is authorized to create PVCs. To mitigate, do not create PVCs with the "cdi.kubevirt.io/storage.import.source: "registry"" annotation and do not create DataVolumes that use the "registry" source.