Kong Kubernetes Ingress Controller cluster-wide ingress configuration DoS via CA-certificate ID collision
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 3.4.18 and 3.5.11.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| >=3.4.0 <3.4.18, >=3.5.0 <3.5.11 | 3.4.18, 3.5.11 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket