Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

CVE-2024-5321

MEDIUM

CVE-2024-5321 is a medium-severity (CVSS 6.1) Incorrect Default Permissions vulnerability in k8s.io/kubernetes. O3 Security confirms whether CVE-2024-5321 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Incorrect permissions on Windows containers logs

Also known asGHSA-82m2-cv7p-4m75GO-2024-2994
Published
Jul 18, 2024
Updated
Jul 15, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed

Real-World Exposure

4 pkgs affected
🐹k8s.io/kubernetes🐹k8s.io/kubernetes🐹k8s.io/kubernetes🐹k8s.io/kubernetes

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐹Gok8s.io/kubernetesall versions1.27.16
🐹Gok8s.io/kubernetes1.28.0&&< 1.28.121.28.12
🐹Gok8s.io/kubernetes1.29.0&&< 1.29.71.29.7
🐹Gok8s.io/kubernetes1.30.0&&< 1.30.31.30.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for k8s.io/kubernetes. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update k8s.io/kubernetes to 1.27.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-5321 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2024-5321 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-5321. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2024-5321 in your dependencies?

O3 detects CVE-2024-5321 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.