Bypassing enforce mountable secrets policy imposed by the ServiceAccount admission plugin
Kubernetes
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| k8s.io/kubernetes Go |
|
|
Kubernetes
| Product | Affected | Fixed in |
|---|---|---|
| k8s.io/kubernetes Go |
|
|
Users may be able to launch containers that bypass the mountable secrets policy enforced by the ServiceAccount admission plugin when using ephemeral containers. The policy ensures pods running with a service account may only reference secrets specified in the service account’s secrets field. Kubernetes clusters are only affected if the ServiceAccount admission plugin and the `kubernetes.io/enforce-mountable-secrets` annotation are used together with ephemeral containers.
From the CVE record · kubernetes
The ServiceAccount admission plugin may fail to enforce the mountable secrets policy for ephemeral containers. Users may be able to launch containers that reference secrets not specified in the service account’s secrets field. Clusters are affected only when the plugin, the `kubernetes.io/enforce-mountable-secrets` annotation, and ephemeral containers are used together.
Operators of Kubernetes clusters using the Go package `k8s.io/kubernetes` should check versions >=1.27.0 <1.27.3, >=1.26.0 <1.26.6, >=1.25.0 <1.25.11, or <1.24.15.