First published: Fri Jun 19 2020(Updated: )
A flaw was found in kubevirt 0.29 and earlier. Virtual Machine Instances (VMIs) can be used to gain access to the host's filesystem. Successful exploitation allows an attacker to assume the privileges of the VM process on the host system. In worst-case scenarios an attacker can read and modify any file on the system where the VMI is running. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/kubevirt | <0.30 | 0.30 |
go/kubevirt.io/kubevirt | <0.30.0 | 0.30.0 |
Kubevirt Kubevirt Kubernetes | <=0.29 | |
Redhat Openshift Virtualization | =1 |
This flaw can be partially or completely mitigated by leveraging existing mechanisms to restrict the VMI process such as running as non-root and using SELinux and sVirt whenever possible.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this flaw is CVE-2020-14316.
CVE-2020-14316 has a severity rating of critical.
Versions of kubevirt up to 0.30 are affected by CVE-2020-14316.
An attacker can use Virtual Machine Instances (VMIs) to gain access to the host's filesystem and assume the privileges of the VM process on the host system.
Yes, a fix is available in kubevirt version 0.30.