CyberRota Analysis
AI-GeneratedThe Kong Kubernetes Ingress Controller is vulnerable to a denial of service due to its handling of CA-certificate Secrets, which can be created by users with namespace-scoped privileges. This flaw allows malicious users to introduce duplicate CA-certificate IDs, leading to the rejection of the entire ingress configuration and disrupting ingress changes across the cluster. Organizations using Kubernetes with the Kong Ingress Controller should prioritize addressing this vulnerability to prevent potential service outages.
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
Kong Kubernetes Ingress Controller (KIC) allows a user with namespace-scoped Secret creation privileges to cause a cluster-wide ingress configuration denial of service. KIC collects CA-certificate Secrets across all watched namespaces using a label selector alone, without ingress-class or namespace restrictions. The CA-certificate primary key is derived from a user-supplied field in the Secret. Duplicate CA-certificate IDs cause Kong Gateway to reject the entire configuration document and halting all ingress changes cluster-wide.