Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation
- 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.28.1, 1.27.5, 1.26.8, 1.25.13, 1.24.17, and 5 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they include Windows nodes.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Kubernetes kubelet
From v1.27.0 · through v1.27.4; From v1.26.0 · through v1.26.7; From v1.25.0 · through v1.25.12; through v1.24.16
- k8s.io/kubernetesGo
From 1.28.0 · fixed in 1.28.1
- k8s.io/kubernetesGo
From 1.27.0 · fixed in 1.27.5
- k8s.io/kubernetesGo
From 1.26.0 · fixed in 1.26.8
- k8s.io/kubernetesGo
From 1.25.0 · fixed in 1.25.13
- k8s.io/kubernetesGo
fixed in 1.24.17
- k8s.io/kubernetesGo
fixed in 1.24.17; From 1.25.0 · fixed in 1.25.13; From 1.26.0 · fixed in 1.26.8; From 1.27.0 · fixed in 1.27.5; From 1.28.0 · fixed in 1.28.1
- k8s.io/mount-utilsGo
fixed in 0.24.17; From 0.25.0 · fixed in 0.25.13; From 0.26.0 · fixed in 0.26.8; From 0.27.0 · fixed in 0.27.5; From 0.28.0 · fixed in 0.28.1