Improper input validation in github.com/openshift/apiserver-library-go
Low-privileged users can 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.
02 / AFFECTED SOFTWARE
Affected packages
04 / EVIDENCE
Source records
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.
Low-privileged users can 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.
05 / REFERENCES
Further evidence
- github.com/openshift/apiserver-library-go
- https://bugzilla.redhat.com/show_bug.cgi?id=2160349
- https://github.com/openshift/apiserver-library-go/commit/30f75d79e424ca462c6de53ee8b93f91183763e6
- https://github.com/openshift/apiserver-library-go/pull/97
- https://nvd.nist.gov/vuln/detail/CVE-2023-0229
- https://github.com/advisories/GHSA-5465-xc2j-6p84