# CVE-2023-0229: github.com/openshift/apiserver-library-go Improper Input Validation vulnerability > Low-privileged users can bypass seccomp restrictions by setting pod profiles to unconfined, weakening container isolation in OpenShift clusters. - **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 25 Jan 2023 - **Updated:** 1 Apr 2025 - **Also known as:** GHSA-5465-xc2j-6p84, GO-2023-1549, RHBA-2023:1037 ## What is CVE-2023-0229? CVE-2023-0229 is a medium-severity vulnerability in Redhat Openshift, published on 25 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A flaw was found in github.com/openshift/apiserver-library-go, used in OpenShift 4.12 and 4.11, that contains an issue that can allow low-privileged users to set the seccomp profile for pods they control to "unconfined." By default, the seccomp profile used in the restricted-v2 Security Context Constraint (SCC) is "runtime/default," allowing users to disable seccomp for pods they can create and modify. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2023-0229? 3 open source packages ship an affected version, including github.com/openshift/apiserver-library-go. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/openshift/apiserver-library-go` | Go | All versions | 0.0.0-20230119093715-30f75d79e424 | | `github.com/openshift/apiserver-library-go` | Go | All versions | 0.0.0-20230120221150-cefee9e0162b | | `github.com/openshift/apiserver-library-go` | Go | All versions | 0.0.0-20230120221150-cefee9e0162b | | `microshift` | Red Hat:openshift:4.12::el8 | All versions | 0:4.12.6-202303012057.p0.g50997a2.assembly.4.12.6.el8 | | `microshift-networking` | Red Hat:openshift:4.12::el8 | All versions | 0:4.12.6-202303012057.p0.g50997a2.assembly.4.12.6.el8 | | `microshift-release-info` | Red Hat:openshift:4.12::el8 | All versions | 0:4.12.6-202303012057.p0.g50997a2.assembly.4.12.6.el8 | | `microshift-selinux` | Red Hat:openshift:4.12::el8 | All versions | 0:4.12.6-202303012057.p0.g50997a2.assembly.4.12.6.el8 | Products: Redhat Openshift. ## How do I fix CVE-2023-0229? Upgrade github.com/openshift/apiserver-library-go to a fixed version for your release line: 0.0.0-20230119093715-30f75d79e424 or 0.0.0-20230120221150-cefee9e0162b. ## Is CVE-2023-0229 being exploited? There is no known exploitation of CVE-2023-0229 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Openshift - [CVE-2014-3496](https://insights.sbomify.com/CVE-2014-3496/): Command injection in n/a (critical 10.0) - [CVE-2014-0234](https://insights.sbomify.com/CVE-2014-0234/): Hardcoded credentials in Red Hat OpenShift Enterprise (critical 9.8) - [CVE-2013-2060](https://insights.sbomify.com/CVE-2013-2060/): Command injection in OpenShift Origin (critical 9.8) - [CVE-2013-4561](https://insights.sbomify.com/CVE-2013-4561/): Path traversal in openshift-origin-msg-node-mcollective (critical 9.1) - [CVE-2014-0163](https://insights.sbomify.com/CVE-2014-0163/): Command injection in Openshift (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-0229 and fix it if it is affected. What it is: CVE-2023-0229 is a medium-severity vulnerability in Redhat Openshift, published on 25 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-0229 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/openshift/apiserver-library-go (Go): affected all versions; fixed in 0.0.0-20230119093715-30f75d79e424 - github.com/openshift/apiserver-library-go (Go): affected all versions; fixed in 0.0.0-20230120221150-cefee9e0162b - github.com/openshift/apiserver-library-go (Go): affected all versions; fixed in 0.0.0-20230120221150-cefee9e0162b 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-0229/ (Markdown: https://insights.sbomify.com/CVE-2023-0229/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-0229 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-0229 - OSV: https://osv.dev/vulnerability/CVE-2023-0229 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-0229/ Summaries are generated and may contain mistakes; the official description above is the record.