Authenticated seccomp bypass via unchecked pod profile
Published Jan 25, 2023 · Updated Apr 1, 2025
Improper input validation in Red Hat OpenShift Container Platform 4.11 and 4.12 allows remote authenticated users to disable pod seccomp. The restricted-v2 SCC admission path accepts a pod's unconfined seccomp profile instead of enforcing its runtime/default policy. A user who can create or modify pods can remove the syscall filter from controlled workloads, weakening their intended isolation from the Linux kernel.
Summary
What happened
Improper input validation in Red Hat OpenShift Container Platform 4.11 and 4.12 allows remote authenticated users to disable pod seccomp. The restricted-v2 SCC admission path accepts a pod's unconfined seccomp profile instead of enforcing its runtime/default policy. A user who can create or modify pods can remove the syscall filter from controlled workloads, weakening their intended isolation from the Linux kernel.
The record
- CVE
- CVE-2023-0229
- Published
- Jan 25, 2023
- Updated
- Apr 1, 2025
- Vendor
- Red Hat
- Product
- Red Hat OpenShift Container Platform
- Classifications
- CWE-20, T1562.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 25, 2023CVE publishedPublication date reported by the CVE source.
- Apr 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=openshift/apiserver-library-go 4.11
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo