Kyverno resource with a deletionTimestamp may allow policy circumvention
cve-program · CVE-2023-34091
PublishedKyverno is a policy engine designed for Kubernetes. In versions of Kyverno prior to 1.10.0, resources which have the `deletionTimestamp` field defined can bypass validate, generate, or mutate-existing policies, even in cases where the `validationFailureAction` field is set to `Enforce`. This situation occurs as resources pending deletion were being consciously exempted by Kyverno, as a way to reduce processing load as policies are typically not applied to objects which are being deleted. However, this could potentially result in allowing a malicious user to leverage the Kubernetes finalizers feature by setting a finalizer which causes the Kubernetes API server to set the `deletionTimestamp` and then not completing the delete operation as a way to explicitly to bypass a Kyverno policy. Note that this is not applicable to Kubernetes Pods but, as an example, a Kubernetes Service resource can be manipulated using an indefinite finalizer to bypass policies. This is resolved in Kyverno 1.10.0. There is no known workaround.
Read the publisher's advisoryeuvd · EUVD-2023-1825
PublishedKyverno is a policy engine designed for Kubernetes. In versions of Kyverno prior to 1.10.0, resources which have the `deletionTimestamp` field defined can bypass validate, generate, or mutate-existing policies, even in cases where the `validationFailureAction` field is set to `Enforce`. This situation occurs as resources pending deletion were being consciously exempted by Kyverno, as a way to reduce processing load as policies are typically not applied to objects which are being deleted. However, this could potentially result in allowing a malicious user to leverage the Kubernetes finalizers feature by setting a finalizer which causes the Kubernetes API server to set the `deletionTimestamp` and then not completing the delete operation as a way to explicitly to bypass a Kyverno policy. Note that this is not applicable to Kubernetes Pods but, as an example, a Kubernetes Service resource can be manipulated using an indefinite finalizer to bypass policies. This is resolved in Kyverno 1.10.0. There is no known workaround.
Read the publisher's advisorynvd · CVE-2023-34091
PublishedKyverno is a policy engine designed for Kubernetes. In versions of Kyverno prior to 1.10.0, resources which have the `deletionTimestamp` field defined can bypass validate, generate, or mutate-existing policies, even in cases where the `validationFailureAction` field is set to `Enforce`. This situation occurs as resources pending deletion were being consciously exempted by Kyverno, as a way to reduce processing load as policies are typically not applied to objects which are being deleted. However, this could potentially result in allowing a malicious user to leverage the Kubernetes finalizers feature by setting a finalizer which causes the Kubernetes API server to set the `deletionTimestamp` and then not completing the delete operation as a way to explicitly to bypass a Kyverno policy. Note that this is not applicable to Kubernetes Pods but, as an example, a Kubernetes Service resource can be manipulated using an indefinite finalizer to bypass policies. This is resolved in Kyverno 1.10.0. There is no known workaround.
Read the publisher's advisoryosv · GHSA-hq4m-4948-64cc
Published### Impact In versions of Kyverno prior to 1.10.0, resources which have the `deletionTimestamp` field defined can bypass validate, generate, or mutate-existing policies, even in cases where the `validationFailureAction` field is set to `Enforce`. This situation occurs as resources pending deletion were being consciously exempted by Kyverno, as a way to reduce processing load as policies are typically not applied to objects which are being deleted. However, this could potentially result in allowing a malicious user to leverage the [Kubernetes finalizers feature](https://kubernetes.io/docs/concepts/overview/working-with-objects/finalizers/) by setting a finalizer which causes the Kubernetes API server to set the `deletionTimestamp` and then not completing the delete operation as a way to explicitly to bypass a Kyverno policy. Note that this is not applicable to Kubernetes Pods but, as an example, a Kubernetes Service resource can be manipulated using an indefinite finalizer to bypass policies. ### Patches This is resolved in Kyverno 1.10.0. ### Workarounds There is no known workaround. ### References _Are there any links users can visit to find out more?_
Read the publisher's advisoryosv · GO-2023-1819
PublishedKyverno resource with a deletionTimestamp may allow policy circumvention 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-34091 · CVE overview and exploitation status
cve-program · CVE-2023-34091
- https://github.com/kyverno/kyverno/security/advisories/GHSA-hq4m-4948-64cc
- https://github.com/kyverno/kyverno/releases/tag/v1.10.0
euvd · EUVD-2023-1825
- https://github.com/kyverno/kyverno/security/advisories/GHSA-hq4m-4948-64cc
- https://github.com/kyverno/kyverno/releases/tag/v1.10.0
nvd · CVE-2023-34091
- https://github.com/kyverno/kyverno/releases/tag/v1.10.0
- https://github.com/kyverno/kyverno/security/advisories/GHSA-hq4m-4948-64cc
osv · GHSA-hq4m-4948-64cc
- https://github.com/kyverno/kyverno/security/advisories/GHSA-hq4m-4948-64cc
- https://nvd.nist.gov/vuln/detail/CVE-2023-34091
- https://github.com/kyverno/kyverno
- https://github.com/kyverno/kyverno/releases/tag/v1.10.0
osv · GO-2023-1819
Related changes
Linked by CVE identifierNo related changes are available here.