Bypassing mountable secrets policy imposed by the ServiceAccount admission plugin
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.27.13, 1.29.4, 1.28.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Kubernetes Kubernetes
through 1.27.12
- k8s.io/kubernetesGo
fixed in 1.27.13
- k8s.io/kubernetesGo
From 1.29.0 · fixed in 1.29.4
- k8s.io/kubernetesGo
From 1.28.0 · fixed in 1.28.9
- k8s.io/kubernetesGo
fixed in 1.27.13; From 1.28.0 · fixed in 1.28.9; From 1.29.0 · fixed in 1.29.4