Skip to content
Fencer Vulns
medium 6.1

CVE-2023-42813 json

Denial of service from malicious manifest in kyverno

published 2023-11-13 2 y ago modified 2026-06-17 4 mo ago also GHSA-wc3x-5rfv-hh5v , GO-2023-2335 , EUVD-2023-47236

cvss
6.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 51%
public exploits
0
none known

Summary

Kyverno is a policy engine designed for Kubernetes. A security vulnerability was found in Kyverno where an attacker could cause denial of service of Kyverno. The vulnerable component in Kyvernos Notary verifier. An attacker would need control over the registry from which Kyverno would fetch attestations. With such a position, the attacker could return a malicious response to Kyverno, when Kyverno would send a request to the registry. The malicious response would cause denial of service of Kyverno, such that other users' admission requests would be blocked from being processed. This is a vulnerability in a new component released in v1.11.0. The only users affected by this are those that have been building Kyverno from source at the main branch which is not encouraged. Users consuming official Kyverno releases are not affected. There are no known cases of this vulnerability being exploited in the wild.

Patch / fix

  • go github.com/kyverno/kyverno 1.5.0-rc1.0.20230918070231-fec2992e3f9f

Exploit prediction

0.66% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:N/A:H
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/kyverno/kyverno
>=1.5.0-rc1.0.20230601080528-80d139bb5d1d, <1.5.0-rc1.0.20230918070231-fec2992e3f9f
1.5.0-rc1.0.20230918070231-fec2992e3f9f

Affected products

  • kyverno kyverno

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.