How severe is CVE-2023-0229?

CVE-2023-0229 has a CVSS score of 6.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-0229?

CVE-2023-0229 affects the following packages: github.com/openshift/apiserver-library-go (Go). Ecosystems affected: Go.

How do I fix CVE-2023-0229?

Update github.com/openshift/apiserver-library-go to 0.0.0-20230120221150-cefee9e0162b or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-0229 is resolved across your whole dependency graph.

How do I detect CVE-2023-0229 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openshift/apiserver-library-go, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-0229 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2023-0229 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-0229 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-0229?

CVE-2023-0229 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 51th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-0229?

CVE-2023-0229 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-0229 published, and has it been updated?

CVE-2023-0229 was published on January 26, 2023 and was last updated on May 20, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2023-0229 — apiserver-library-go

MEDIUMFix: openshift/apiserver-library-go#97

CVE-2023-0229 is a medium-severity (CVSS 6.3) Improper Input Validation vulnerability in github.com/openshift/apiserver-library-go. A fix is available for github.com/openshift/apiserver-library-go — see the affected versions and patch details below.

github.com/openshift/apiserver-library-go Improper Input Validation vulnerability

Also known asGO-2023-1549

Published

Jan 26, 2023

Updated

May 20, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-0229.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs51th percentile — riskier than 51% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹github.com/openshift/apiserver-library-go

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/openshift/apiserver-library-go`	all versions	0.0.0-20230120221150-cefee9e0162b`go get github.com/openshift/apiserver-library-go@v0.0.0-20230120221150-cefee9e0162b`

Affected Products

1 product · 2 configurations

Application

openshiftredhat

2 versions

4.114.12

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openshift/apiserver-library-go, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/openshift/apiserver-library-go to 0.0.0-20230120221150-cefee9e0162b or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-0229 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This flaw does not affect OpenShift versions 4.10 and earlier.

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 4.12	`microshift-0:4.12.6-202303012057.p0.g50997a2.assembly.4.12.6.el8`	RHBA-2023:1037
Red Hat OpenShift Container Platform 4.13	`openshift-0:4.13.0-202304211155.p0.gb404935.assembly.stream.el8`	RHSA-2023:1325

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-0229 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

Low

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

CWE Classification

CWE-20Improper Input Validation

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jan 26, 2023

Last updated

May 20, 2024

Identifiers

CVE-2023-0229

GO-2023-1549

References

Advisorynvd.nist.gov · CVE 2023 0229 Webgithub.com Webgithub.com · 30f75d79e424ca462c6de53ee8b93f91183763e6 Webbugzilla.redhat.com · show bug.cgi Packagegithub.com/openshift/apiserver

Related vulnerabilities

Also affects apiserver-library-go

This CVE is medium severity; 1 of 1 other CVE affecting apiserver-library-go is rated as high or higher (top: high).

CVE-2023-1260

Same weakness: CWE-20

This CVE is medium severity; 5 of 7 other CVEs with CWE-20 are rated as high or higher (top: high).

CVE-2026-44265CVE-2026-119280CVE-2026-96631CVE-2026-119210CVE-2026-59978GHSA-c33x-vcv4-vg3gCVE-2026-115915Browse all CWE-20

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedMay 20, 2024