CVE-2020-1701: Medium severity kubevirt vulnerability
A flaw was found in the KubeVirt main virt-handler versions before 0.26.0 regarding the access permissions of virt-handler. An attacker with access to create VMs could attach any secret within their namespace, allowing them to read the contents of that secret.
Other sources
A flaw was found in the kubevirt main virt-handler. Due to the access permissions of virt-handler an attacker with access to create vms could attach any secret within their namespace. This would allow them to read the contents of that secret.
Upstream issue:
https://github.com/kubevirt/kubevirt/issues/2967
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the vulnerability ID for this flaw?
The vulnerability ID for this flaw is CVE-2020-1701.
What software versions are affected by this vulnerability?
Versions before 0.26.0 of KubeVirt main virt-handler and Kubevirt are affected by this vulnerability.
What is the severity of CVE-2020-1701?
The severity of CVE-2020-1701 is medium.
How can an attacker exploit this vulnerability?
An attacker with access to create VMs could attach any secret within their namespace, allowing them to read the contents of that secret.
Is there a fix available for this vulnerability?
Yes, the fix for this vulnerability is to upgrade to version 0.26.0 of KubeVirt main virt-handler.