CVE-2020-2025 — Kata Containers - Cloud Hypervisor guests persist filesystem changes to the underlying host image file

Kata Containers before 1.11.0 on Cloud Hypervisor persists guest filesystem changes to the underlying image file on the host. A malicious guest can overwrite the image file to gain control of all subsequent guest VMs. Since Kata Containers uses the same VM image file with all VMMs, this issue may also affect QEMU and Firecracker based guests.

Published May 19, 2020Updated Sep 16, 2024Sources: cvelistV5, palo_alto

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

chance of exploitation in 30 days

Affects

kata containers

kata_containers

CVSS base

8.8

HIGH

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

kata containers

Products (1)

kata containers

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
8.8	CVSS 3.1	HIGH	—	—	cvelistV5

Weakness & attack patterns

CWE-284

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

T1027.009Obfuscated Files or Information: Embedded Payloads
T1546.004Event Triggered Execution: .bash_profile and .bashrc
T1546.016Event Triggered Execution: Installer Packages

References

1 on the record

github.com/kata-containers/runtime/pull/2487
x_refsource_MISC

Elsewhere on this site

kata containersevery CVE for this vendor
CWE-284other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.