Database/Container, Kubernetes & orchestration
Kubernetes (kube-apiserver): Init/ephemeral container envFrom bypasses the ServiceAccount mountable-secrets policy
CVSS 2.7CVE-2024-3177Container, Kubernetes & orchestrationcurated
Impact
Init/ephemeral container envFrom bypasses the ServiceAccount mountable-secrets policy
Who can reach it
Cluster user with namespace access
What to do
Rolling control-plane upgrade; no GPU drain
Fleet impact
How widespread
Universal component, low impact - every cluster runs the ServiceAccount admission plugin
Cost to remediate
daemon-restart - control-plane-only upgrade, no GPU node drain needed
Why it hits the whole fleet
envFrom bypasses the mountable-secrets restriction, leaking secrets across a namespace boundary; control-plane-scoped and low severity, so not a fleet emergency
References
Related entries
- Kubernetes (kube-apiserver): Nodes can bypass DRA authorization checksCVE-2025-4563 · Kubernetes (kube-apiserver)Low
- Kubernetes (kube-apiserver): TOCTOU/DNS-rebinding bypass of the link-local and localhost proxy protectionsCVE-2020-8562 · Kubernetes (kube-apiserver)Low
- Kubernetes (kube-apiserver): Cluster-scoped custom resources reachable through namespaced requests, so namespace-scopedCVE-2019-11247 · Kubernetes (kube-apiserver)High
- Kubernetes (kube-apiserver): "Billion laughs": malicious YAML/JSON payload consumes all apiserver memoryCVE-2019-11253 · Kubernetes (kube-apiserver)High
- Kubernetes (kube-apiserver): A node can delete itself, and cascade-delete other objects, by adding an OwnerReferenceCVE-2025-5187 · Kubernetes (kube-apiserver)Medium
- Kubernetes (kube-apiserver): Node address not verified when proxyingCVE-2022-3294 · Kubernetes (kube-apiserver)Medium
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.