Kubernetes allows bypassing mountable secrets policy imposed by the ServiceAccount admission plugin
Low severity
GitHub Reviewed
Published
Apr 23, 2024
to the GitHub Advisory Database
•
Updated May 2, 2024
Package
Affected versions
< 1.27.13
>= 1.29.0, <= 1.29.3
>= 1.28.0, <= 1.28.8
Patched versions
1.27.13
1.29.4
1.28.9
Description
Published by the National Vulnerability Database
Apr 22, 2024
Published to the GitHub Advisory Database
Apr 23, 2024
Reviewed
Apr 23, 2024
Last updated
May 2, 2024
A security issue was discovered in Kubernetes where users may be able to launch containers that bypass the mountable secrets policy enforced by the ServiceAccount admission plugin when using containers, init containers, and ephemeral containers with the envFrom field populated. 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 containers, init containers, and ephemeral containers with the envFrom field populated.
References