CyberRota Analysis
AI-GeneratedThe vulnerability affects the containerized-data-importer (CDI) by misconfiguring the aggregated cdi.kubevirt.io:view ClusterRole, which inadvertently allows users with read-only access to create DataVolume clones, thereby enabling them to exfiltrate data from any Persistent Volume Claim (PVC) within the cluster. This flaw undermines namespace isolation and the intended read-only restrictions, posing a significant risk of data leakage. Organizations utilizing CDI, particularly those with broad ClusterRoleBindings, should prioritize addressing this vulnerability to safeguard sensitive data.
Original NVD Description
In containerized-data-importer (CDI), the aggregated cdi.kubevirt.io:view ClusterRole, intended to provide read-only access to CDI resources, includes a rule granting create on the datavolumes/source subresource. CDI's DataVolume clone authorization accepts this permission as sufficient to authorize cloning the contents of any PVC the caller can name, without requiring write access to the source namespace. A user or service account bound to the view role, commonly granted cluster-wide via ClusterRoleBinding, who also has ordinary write access (edit/admin) to any single namespace, can use this to exfiltrate the contents of any PVC in the cluster into a namespace they control, bypassing namespace isolation and the read-only guarantee of the view role.