Kyverno versions before 1.19.2 have an authorization bypass vulnerability that allows namespaced tenants to generate arbitrary resource kinds in any namespace by exploiting variable templating in the generate rule. This can lead to unauthorized creation of NetworkPolicies or RoleBindings in sensitive namespaces such as victim namespaces or kube-system. The issue is fixed in version 1.19.2.
Kyverno versions 1.19.1 before 1.19.2 contain an authorization bypass vulnerability in the apiCall namespace clamp. This flaw allows namespace tenants to bypass namespace restrictions by appending malformed percent-escapes to the urlPath, enabling cross-namespace and cluster-scoped API requests. Exploitation can lead to attackers creating namespaced Policies that run with admission-controller ServiceAccount privileges, allowing them to read resources in other namespaces and create mutating webhooks, effectively escalating privileges to cluster admin.
Kyverno versions from 1.11.0 up to but not including 1.19.2 contain an unbounded decompression vulnerability in the FetchSignatureBlob function. This flaw allows attackers who control registry referrers or signatures to supply highly compressed notary signature layers that decompress beyond the allowed maximum payload size. Exploiting this can cause the admission controller to exhaust memory, leading to out-of-memory (OOM) kills and denial of service conditions. The vulnerability is fixed in version 1.19.2.
Kyverno versions from 1.11.0 up to but not including 1.19.2 contain an unbounded decompression vulnerability in the extractStatement function. This flaw allows remote attackers who control registry referrer artifacts to supply highly compressed attestation layers that decompress to sizes exceeding the configured maximum payload size. Exploiting this can cause the admission controller to exhaust memory, leading to out-of-memory (OOM) kills and denial of service conditions.
Kyverno versions 1.18.0 up to but not including 1.19.2 contain a vulnerability in the verifyImages feature where cached signature verification results are incorrectly keyed by image reference strings rather than the verified digest. This allows an attacker who can submit workloads and manipulate registry tags to bypass signature and attestation checks, potentially admitting unverified images.
Kyverno versions prior to 1.19.2 have a missing authorization vulnerability that allows namespaced Policy authors to read resources in other namespaces. By exploiting templating of generate.clone or cloneList namespace values, an attacker can cause the background-controller to copy sensitive ConfigMaps from a victim namespace into the attacker's namespace, leading to cross-tenant data disclosure.
Kyverno versions before 1.19.2 contain a denial-of-service vulnerability in the In and NotIn operators. This flaw allows attackers to crash the policy engine by submitting resources that cause a panic due to unchecked type assertions when JMESPath-evaluated values yield arrays of integers, booleans, or mixed types. The resulting panic disrupts admission control and policy enforcement. The issue is fixed in version 1.19.2.
Kyverno versions before 1.19.2 contain an authentication bypass vulnerability in the matchCertificateData function. This flaw allows attackers with a leaf certificate from a configured private trust root to bypass subject and subjectRegExp checks if the signing certificate lacks a Subject Alternative Name (SAN). By omitting the SAN and setting the expected Fulcio issuer OID, attackers can sign malicious images that bypass signer pinning. The issue is fixed in version 1.19.2.
Kyverno versions from 1.17.0 up to but not including 1.19.2 have a missing authorization vulnerability in the mutate-existing background processor. This flaw allows namespaced tenants to modify resources outside their own namespace by creating a NamespacedMutatingPolicy that targets Namespace objects or resources in other namespaces. Exploitation can lead to cluster-wide removal of Pod Security labels by the background-controller ServiceAccount.
Kyverno versions prior to 1.19.2 contain a vulnerability in the buildStatementMap function where an unchecked type assertion allows unauthenticated attackers to crash the policy engine by submitting crafted attestation statements. This flaw can be exploited by pushing an OCI referrer manifest with a non-string type field, which may bypass image verification when failurePolicy is set to Ignore or cause a crash-loop in the reports-controller.
Kyverno versions prior to 1.19.2 have a vulnerability in the variable-substitution engine where an unchecked type assertion can cause a panic. This occurs when users submit resources with non-string fields referenced by shallow variable substitution in policies, leading to a denial of service of the webhook and potential policy bypass if failurePolicy is set to Ignore. The issue is fixed in version 1.19.2.
Kyverno versions from 1.17.0 up to but not including 1.19.2 contain a critical privilege escalation vulnerability. This flaw allows namespace-scoped tenants to modify resources in other namespaces by exploiting a NamespacedMutatingPolicy that lacks proper namespace checks in its targetMatchConstraints.expression. Attackers can manipulate cluster-wide background controllers to alter RoleBindings, Roles, NetworkPolicies, and ConfigMaps in other namespaces. The vulnerability is fixed in version 1.19.2.
Kyverno versions from 1.19.1 before 1.19.2 contain a namespace isolation bypass vulnerability in the APICall Fetch() function. This occurs because the path.Clean function incorrectly treats the '?' character as part of the path, allowing a crafted URLPath query string to bypass namespace restrictions. An attacker with permission to create namespaced policies can exploit this to access cluster-scoped resources outside their namespace.
Kyverno versions from 1.16.0 up to but not including 1.19.2 contain a path traversal vulnerability in the resource argument of resource.get() and resource.post() within namespaced CEL policies. This flaw allows tenants with the ability to create NamespacedValidatingPolicy resources to escape their namespace restrictions by inserting '..' path segments, enabling unauthorized read and write access to arbitrary cluster objects. Exploitation can lead to cluster takeover. The issue is fixed in version 1.19.2.
Kyverno versions from 1.19.1 up to but not including 1.19.2 contain a privilege escalation vulnerability. This flaw allows a namespace-scoped user who can create a Policy to exploit improper validation of the Policy's context.apiCall urlPath. By hiding '../' segments behind URL fragments or queries, the user can access cluster-scoped endpoints using Kyverno's ServiceAccount, effectively gaining cluster admin privileges. The issue is fixed in version 1.19.2.
Kyverno versions prior to 1.19.2 contain a denial of service vulnerability where namespace-scoped policy authors can exhaust CPU and memory resources by submitting CEL expressions without runtime cost limits. This can cause Kyverno pods to be OOM-killed and block cluster-wide admission.
Kyverno versions before 1.19.2 have an authorization bypass vulnerability in the Generation Handler. This flaw allows users with create or update permissions to spoof internal labels and trigger synchronized generate policies. Exploitation can lead to cloning sensitive Secrets from restricted namespaces into an attacker-controlled namespace by labeling a ConfigMap as managed by Kyverno with crafted labels.
Kyverno versions prior to 1.19.2 have a policy bypass vulnerability in the admissionpolicygenerator controller. This flaw allows users with namespaced create rights on PolicyExceptions to inject negated matchConditions into generated ValidatingAdmissionPolicies, bypassing cluster-wide policy enforcement. The vulnerability arises because the controller improperly folds PolicyExceptions into generated policies while ignoring certain configuration gates. A fix is available in version 1.19.2.
A vulnerability in Kibana allows an authenticated user with read access to connectors in one space to access connector execution log information from other spaces without proper authorization. This leads to information disclosure including connector names, identifiers, execution status, timestamps, error messages, and aggregated execution statistics. The issue is due to authorization bypass through a user-controlled key. Fixed versions are available.
Kyverno versions prior to 1.19.2 contain a denial of service vulnerability where namespaced policy authors can submit specially crafted wildcard patterns. This causes excessive CPU consumption in the admission controller, leading to cluster-wide webhook timeouts that block resource operations. The issue is fixed in version 1.19.2.