CyberRota Analysis
AI-GeneratedKubernetes versions prior to 0.26.22 are vulnerable to a denial-of-service condition in the Skipper HTTP router, where an attacker with in-cluster network access can exploit the admission endpoint by sending excessively large request bodies, leading to unbounded memory allocation and potential out-of-memory termination of the Skipper process. While the impact is limited to Ingress and RouteGroup admission, affected users should prioritize upgrading to version 0.26.22 to mitigate this risk. Organizations utilizing Skipper in their Kubernetes environments, especially those with sensitive workloads, should address this vulnerability promptly.
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
Skipper is an HTTP router and reverse proxy for service composition. Prior to 0.26.22, Handler in dataclients/kubernetes/admission/admission.go passes the body of requests to the Kubernetes admission endpoint at :9443/admission directly to io.ReadAll(r.Body) without a size limit. An attacker with in-cluster network access and a valid Kubernetes client certificate can send a very large body that causes unbounded memory allocation and an out-of-memory termination of the Skipper process. The disruption is limited to Ingress and RouteGroup admission rather than pod creation or unrelated admission controllers, and Kubernetes normally restarts the process. This issue is fixed in version 0.26.22.