CVE-2023-2431GO-2023-1864GHSA-XC8M-28VV-4PJC
Bypass of seccomp profile enforcement
- 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 v1.24.14, v1.25.9, v1.26.4, v1.27.1, 1.24.14, and 3 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
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
A security issue was discovered in Kubelet that allows pods to bypass the seccomp profile enforcement. Pods that use localhost type for seccomp profile but specify an empty profile field, are affected by this issue. In this scenario, this vulnerability allows the pod to run in unconfined (seccomp disabled) mode. This bug affects Kubelet.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Kubernetes Kubernetes
fixed in v1.24.14; From v1.25.0 · fixed in v1.25.9; From v1.26.0 · fixed in v1.26.4; From v1.27.0 · fixed in v1.27.1
- k8s.io/kubernetesGo
fixed in 1.24.14; From 1.25.0 · fixed in 1.25.10; From 1.26.0 · fixed in 1.26.5; From 1.27.0 · fixed in 1.27.2
- k8s.io/kubernetesGo
fixed in 1.24.14
- k8s.io/kubernetesGo
From 1.25.0 · fixed in 1.25.10
- k8s.io/kubernetesGo
From 1.26.0 · fixed in 1.26.5
- k8s.io/kubernetesGo
From 1.27.0 · fixed in 1.27.2