CVE-2023-34091 Affecting kyverno-fips-1.11 package, versions <1.11.5-r21


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.5% (39th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-KYVERNOFIPS111-9509818
  • published22 Mar 2025
  • disclosed1 Jun 2023

Introduced: 1 Jun 2023

CVE-2023-34091  (opens in a new tab)

How to fix?

Upgrade Chainguard kyverno-fips-1.11 to version 1.11.5-r21 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kyverno-fips-1.11 package and not the kyverno-fips-1.11 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Kyverno 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.

CVSS Base Scores

version 3.1