Advisory

GHSA-hq4m-4948-64cc

Also known as: CVE-2023-34091, GO-2023-1819

Summary

Kyverno resource with a deletionTimestamp may allow policy circumvention

Details

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 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?_

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2023-06-05 17:10 UTC
Modified
2026-08-07 08:12 UTC

Affected packages and fixes

github.com/kyverno/kyverno

Go · All systems

Affected

  • introduced 0, fixed 1.10.0 (semver)

Fixed versions

1.10.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences