CVE-2020-28914
Summary
| CVE | CVE-2020-28914 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2020-11-17 22:15:00 UTC |
| Updated | 2020-12-04 15:25:00 UTC |
| Description | An improper file permissions vulnerability affects Kata Containers prior to 1.11.5. When using a Kubernetes hostPath volume and mounting either a file or directory into a container as readonly, the file/directory is mounted as readOnly inside the container, but is still writable inside the guest. For a container breakout situation, a malicious guest can potentially modify or delete files/directories expected to be read-only. |
Risk And Classification
Problem Types: CWE-732
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Katacontainers | Kata-containers | All | All | All | All |
| Application | Katacontainers | Kata-containers | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Backports: Read-only mount fixes for 1.11 by amshinde · Pull Request #3051 · kata-containers/runtime · GitHub | MISC | github.com | Third Party Advisory |
| Release # Release 1.12.0 · kata-containers/runtime · GitHub | MISC | github.com | Release Notes, Third Party Advisory |
| readonly volume should be bind mounted readonly on the host by bergwolf · Pull Request #3042 · kata-containers/runtime · GitHub | MISC | github.com | Third Party Advisory |
| Release # Release 1.11.5 · kata-containers/runtime · GitHub | MISC | github.com | Release Notes, Third Party Advisory |
| runtime: readonly volume should be bind mounted readonly on the host by bergwolf · Pull Request #1062 · kata-containers/kata-containers · GitHub | MISC | github.com | Third Party Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.