# CVE-2023-2431: Bypass of seccomp profile enforcement > Attackers can bypass seccomp profile enforcement in Kubernetes Kubelet by using an empty localhost profile, allowing pods to run unconfined. - **Severity:** Low 3.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 16 Jun 2023 - **Updated:** 13 Feb 2025 - **Also known as:** DEBIAN-CVE-2023-2431, GHSA-xc8m-28vv-4pjc, GO-2023-1864, SUSE-SU-2023:2691-1, openSUSE-SU-2024:13013-1 ## What is CVE-2023-2431? CVE-2023-2431 is a low-severity vulnerability in Fedoraproject Fedora, published on 16 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. Weakness: CWE-1287 (Improper Validation of Specified Type of Input) ## Which versions are affected by CVE-2023-2431? 9 open source packages ship an affected version, including k8s.io/kubernetes. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `k8s.io/kubernetes` | Go | All versions | 1.24.14, 1.25.10, 1.26.5, 1.27.2 | | `k8s.io/kubernetes` | Go | All versions | 1.24.14 | | `k8s.io/kubernetes` | Go | All versions | 1.24.14 | | `k8s.io/kubernetes` | Go | From 1.25.0 | 1.25.10 | | `k8s.io/kubernetes` | Go | From 1.25.0 | 1.25.10 | | `k8s.io/kubernetes` | Go | From 1.26.0 | 1.26.5 | | `k8s.io/kubernetes` | Go | From 1.26.0 | 1.26.5 | | `k8s.io/kubernetes` | Go | From 1.27.0 | 1.27.2 | | `k8s.io/kubernetes` | Go | From 1.27.0 | 1.27.2 | | `kubernetes1.23` | SUSE:Linux Enterprise Module for Containers 15 SP5 | All versions | 1.23.17-150500.3.6.1 | | `kubernetes1.23` | openSUSE:Leap 15.5 | All versions | 1.23.17-150500.3.6.1 | | `kubernetes1.23` | openSUSE:Tumbleweed | All versions | 1.23.17-5.1 | Products: Fedoraproject Fedora, Kubernetes Kubernetes. ## How do I fix CVE-2023-2431? Upgrade k8s.io/kubernetes to a fixed version for your release line: 1.24.14, 1.25.10, 1.26.5 or 1.27.2. ## Is CVE-2023-2431 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-2431 exists. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-2431 and fix it if it is affected. What it is: CVE-2023-2431 is a low-severity vulnerability in Fedoraproject Fedora, published on 16 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-2431 exists. Affected packages and fixed versions: - k8s.io/kubernetes (Go): affected all versions; fixed in 1.24.14, 1.25.10, 1.26.5, 1.27.2 - k8s.io/kubernetes (Go): affected all versions; fixed in 1.24.14 - k8s.io/kubernetes (Go): affected all versions; fixed in 1.24.14 - k8s.io/kubernetes (Go): affected from 1.25.0; fixed in 1.25.10 - k8s.io/kubernetes (Go): affected from 1.25.0; fixed in 1.25.10 - k8s.io/kubernetes (Go): affected from 1.26.0; fixed in 1.26.5 - k8s.io/kubernetes (Go): affected from 1.26.0; fixed in 1.26.5 - k8s.io/kubernetes (Go): affected from 1.27.0; fixed in 1.27.2 - k8s.io/kubernetes (Go): affected from 1.27.0; fixed in 1.27.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-2431/ (Markdown: https://insights.sbomify.com/CVE-2023-2431/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-2431 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-2431 - OSV: https://osv.dev/vulnerability/CVE-2023-2431 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-2431/ Summaries are generated and may contain mistakes; the official description above is the record.