CVE-2020-2023
CVE-2020-2023 — Kata Containers - Containers have access to the guest root filesystem device
Kata Containers doesn't restrict containers from accessing the guest's root filesystem device. Malicious containers can exploit this to gain code execution on the guest and masquerade as the kata-agent. This issue affects Kata Containers 1.11 versions earlier than 1.11.1; Kata Containers 1.10 versions earlier than 1.10.5; and Kata Containers 1.9 and earlier versions.
Published Updated Sources: 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
Exploit code
public exploit, none observed
EPSS
1%
chance of exploitation in 30 days
CVSS base
3.8
LOW
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)
Products (1)
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 |
|---|---|---|---|---|---|
| 3.8 | CVSS 3.1 | LOW | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-250
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Indexed by
References
7 on the record
- github.com/kata-containers/runtime/pull/2487
x_refsource_MISC
- github.com/kata-containers/runtime/pull/2477
x_refsource_MISC
- github.com/kata-containers/runtime/issues/2488
x_refsource_MISC
- github.com/kata-containers/agent/issues/791
x_refsource_MISC
- github.com/kata-containers/agent/pull/792
x_refsource_MISC
- github.com/kata-containers/runtime/releases/tag/1.11.1
x_refsource_MISC
- github.com/kata-containers/runtime/releases/tag/1.10.5
x_refsource_MISC
Elsewhere on this site
- kata containersevery CVE for this vendor
- CWE-250other 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.