# CVE-2024-5321: Incorrect permissions on Windows containers logs

> Attackers on Windows Kubernetes nodes can read or modify container logs due to incorrect file permissions.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **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:** 18 Jul 2024
- **Updated:** 13 Sep 2024
- **Also known as:** AZL-45436, CLEANSTART-2026-PI46891, CLEANSTART-2026-SA69447, ECHO-ff7b-4bc1-46e0, GHSA-82m2-cv7p-4m75, GO-2024-2994, MINI-32w9-2p3x-xq77

## What is CVE-2024-5321?

CVE-2024-5321 is a medium-severity missing authorization vulnerability in Kubernetes, published on 18 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security issue was discovered in Kubernetes clusters with Windows nodes where BUILTIN\Users may be able to read container logs and NT AUTHORITY\Authenticated Users may be able to modify container logs.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2024-5321?

9 open source packages ship an affected version, including k8s.io/kubernetes.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `k8s.io/kubernetes` | Go | All versions | 1.27.16, 1.28.12, 1.29.7, 1.30.3 |
| `k8s.io/kubernetes` | Go | All versions | 1.27.16 |
| `k8s.io/kubernetes` | Go | All versions | 1.27.16 |
| `k8s.io/kubernetes` | Go | From 1.28.0 | 1.28.12 |
| `k8s.io/kubernetes` | Go | From 1.28.0 | 1.28.12 |
| `k8s.io/kubernetes` | Go | From 1.29.0 | 1.29.7 |
| `k8s.io/kubernetes` | Go | From 1.29.0 | 1.29.7 |
| `k8s.io/kubernetes` | Go | From 1.30.0 | 1.30.3 |
| `k8s.io/kubernetes` | Go | From 1.30.0 | 1.30.3 |

## How do I fix CVE-2024-5321?

Upgrade k8s.io/kubernetes to a fixed version for your release line: 1.27.16, 1.28.12, 1.29.7 or 1.30.3.

## Is CVE-2024-5321 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5321 and fix it if it is affected.

What it is: CVE-2024-5321 is a medium-severity missing authorization vulnerability in Kubernetes, published on 18 Jul 2024. 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-2024-5321 in the wild and no public exploit code.

Affected packages and fixed versions:
- k8s.io/kubernetes (Go): affected all versions; fixed in 1.27.16, 1.28.12, 1.29.7, 1.30.3
- k8s.io/kubernetes (Go): affected all versions; fixed in 1.27.16
- k8s.io/kubernetes (Go): affected all versions; fixed in 1.27.16
- k8s.io/kubernetes (Go): affected from 1.28.0; fixed in 1.28.12
- k8s.io/kubernetes (Go): affected from 1.28.0; fixed in 1.28.12
- k8s.io/kubernetes (Go): affected from 1.29.0; fixed in 1.29.7
- k8s.io/kubernetes (Go): affected from 1.29.0; fixed in 1.29.7
- k8s.io/kubernetes (Go): affected from 1.30.0; fixed in 1.30.3
- k8s.io/kubernetes (Go): affected from 1.30.0; fixed in 1.30.3

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-2024-5321/ (Markdown: https://insights.sbomify.com/CVE-2024-5321/index.md)
```

## Sources

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

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