CyberRota Analysis
AI-GeneratedKyverno versions prior to 1.16.4 are vulnerable due to the automatic inclusion of the admission controller's ServiceAccount token in outbound HTTP requests, which lacks proper authorization headers. This flaw allows attackers to exfiltrate the token by redirecting requests to external endpoints, potentially granting them full control over Kyverno policies and cluster resources. Organizations using Kyverno should prioritize patching to mitigate the risk of unauthorized access and control over their Kubernetes environments.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Kyverno before 1.16.4 automatically attaches the admission controller's ServiceAccount token to outbound HTTP requests in apiCall service mode without explicit authorization headers. Attackers can exfiltrate the token by directing apiCall requests to external or attacker-controlled endpoints, gaining full control over Kyverno policies and cluster resources.