# CVE-2020-28914: Missing authorization in n/a

> Attackers can modify or delete read-only files mounted via Kubernetes hostPath volumes in Kata Containers due to improper guest permissions.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6w62-mvw6-xggx, OESA-2021-1084

## What is CVE-2020-28914?

CVE-2020-28914 is a high-severity missing authorization vulnerability in n/a, published on 17 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2020-28914?

It affects 1 product.


Products: Katacontainers Kata-Containers.

## How do I fix CVE-2020-28914?

Upgrade to a fixed version.

## Is CVE-2020-28914 being exploited?

There is no known exploitation of CVE-2020-28914 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-28914 and fix it if it is affected.

What it is: CVE-2020-28914 is a high-severity missing authorization vulnerability in n/a, published on 17 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-28914 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-28914/ (Markdown: https://insights.sbomify.com/CVE-2020-28914/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-28914
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-28914
- OSV: https://osv.dev/vulnerability/CVE-2020-28914

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-28914/
Summaries are generated and may contain mistakes; the official description above is the record.