Seccomp policy bypass via latest-version misresolution
Published May 30, 2023 · Updated Jan 10, 2025
Security-control bypass in Kyverno 1.9.2 through 1.9.3 allows remote authenticated users to deploy pods without required Seccomp controls. The validate.podSecurity subrule mishandles the latest version value, causing the baseline Pod Security Standards Seccomp check to be skipped instead of evaluated. The bypass requires a policy that selects latest; policies pinned to a numbered Pod Security Standards version remain effective.
Summary
What happened
Security-control bypass in Kyverno 1.9.2 through 1.9.3 allows remote authenticated users to deploy pods without required Seccomp controls. The validate.podSecurity subrule mishandles the latest version value, causing the baseline Pod Security Standards Seccomp check to be skipped instead of evaluated. The bypass requires a policy that selects latest; policies pinned to a numbered Pod Security Standards version remain effective.
The record
- CVE
- CVE-2023-33191
- Published
- May 30, 2023
- Updated
- Jan 10, 2025
- Vendor
- Kyverno
- Product
- Kyverno
- Classifications
- CWE-284, T1562.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 30, 2023CVE publishedPublication date reported by the CVE source.
- Jan 10, 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=>= 1.9.2, < 1.9.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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