kyverno seccomp control can be circumvented
cve-program · CVE-2023-33191
PublishedKyverno is a policy engine designed for Kubernetes. Kyverno seccomp control can be circumvented. Users of the podSecurity `validate.podSecurity` subrule in Kyverno 1.9.2 and 1.9.3 are vulnerable. This issue was patched in version 1.9.4.
Read the publisher's advisoryeuvd · EUVD-2023-1454
PublishedKyverno is a policy engine designed for Kubernetes. Kyverno seccomp control can be circumvented. Users of the podSecurity `validate.podSecurity` subrule in Kyverno 1.9.2 and 1.9.3 are vulnerable. This issue was patched in version 1.9.4.
Read the publisher's advisorynvd · CVE-2023-33191
PublishedKyverno is a policy engine designed for Kubernetes. Kyverno seccomp control can be circumvented. Users of the podSecurity `validate.podSecurity` subrule in Kyverno 1.9.2 and 1.9.3 are vulnerable. This issue was patched in version 1.9.4.
Read the publisher's advisoryosv · GHSA-33hq-f2mf-jm3c
Published### Impact Users of the podSecurity (`validate.podSecurity`) subrule in Kyverno versions v1.9.2 and v1.9.3 may be unable to enforce the check for the Seccomp control at the baseline level when using a `version` value of `latest`. There is no effect if a version number is referenced instead. See the [documentation](https://kyverno.io/docs/writing-policies/validate/#pod-security) for information on this subrule type. Users of Kyverno v1.9.2 and v1.9.3 are affected. ### Patches v1.9.4 v1.10.0 ### Workarounds To work around this issue without upgrading to v1.9.4, temporarily install individual policies for the respective Seccomp checks in baseline [here](https://kyverno.io/policies/pod-security/baseline/restrict-seccomp/restrict-seccomp/) and restricted [here](https://kyverno.io/policies/pod-security/restricted/restrict-seccomp-strict/restrict-seccomp-strict/). ### References * https://kyverno.io/docs/writing-policies/validate/#pod-security * https://github.com/kyverno/kyverno/pull/7263
Read the publisher's advisoryosv · GO-2023-1801
Publishedkyverno seccomp control can be circumvented in github.com/kyverno/kyverno
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2023-33191 · CVE overview and exploitation status
cve-program · CVE-2023-33191
- https://github.com/kyverno/kyverno/security/advisories/GHSA-33hq-f2mf-jm3c
- https://github.com/kyverno/kyverno/pull/7263
- https://github.com/kyverno/kyverno/releases/tag/v1.9.4
euvd · EUVD-2023-1454
- https://github.com/kyverno/kyverno/security/advisories/GHSA-33hq-f2mf-jm3c
- https://github.com/kyverno/kyverno/pull/7263
- https://github.com/kyverno/kyverno/releases/tag/v1.9.4
nvd · CVE-2023-33191
- https://github.com/kyverno/kyverno/pull/7263
- https://github.com/kyverno/kyverno/releases/tag/v1.9.4
- https://github.com/kyverno/kyverno/security/advisories/GHSA-33hq-f2mf-jm3c
osv · GHSA-33hq-f2mf-jm3c
- https://github.com/kyverno/kyverno/security/advisories/GHSA-33hq-f2mf-jm3c
- https://nvd.nist.gov/vuln/detail/CVE-2023-33191
- https://github.com/kyverno/kyverno/pull/7263
- https://github.com/kyverno/kyverno
- https://github.com/kyverno/kyverno/releases/tag/v1.9.4
osv · GO-2023-1801
Related changes
Linked by CVE identifierNo related changes are available here.