Approved changes feed: RSS · Atom

cpe:2.3:a:nirmata:kyverno:*:*:*:*:*:go:*:*

part: a version: * update: *

VendorNirmata (e8956fdf-566b-5207-bc05-355f0b36983e)
ProductKyverno (b3f580a6-9308-512f-bcc3-a34530ee5e60)
Edition*
Language*
Software edition*
Target softwarego
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2024-48921 vulnerable 2026-06-08 06:50:11.706803 Kyverno's PolicyException objects can be created in any namespace by default
Kyverno is a policy engine designed for Kubernetes. A kyverno ClusterPolicy, ie. "disallow-privileged-containers," can be overridden by the creation of a PolicyException in a random namespace. By design, PolicyExceptions are consumed from any namespace. Administrators may not recognize that this allows users with privileges to non-kyverno namespaces to create exceptions. This vulnerability is fixed in 1.13.0.
Published: 2024-10-29T14:14:36.260Z
Updated: 2024-10-29T14:58:36.597Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-34091 vulnerable 2026-06-08 06:06:24.484420 Kyverno resource with a deletionTimestamp may allow policy circumvention
MEDIUM (6.5)
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.
Published: 2023-06-01T16:24:53.920Z
Updated: 2025-01-08T21:32:51.451Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.