CyberRota Analysis
AI-GeneratedKubernetes deployments using Envoy Gateway versions prior to 1.7.4 and 1.8.1 are vulnerable to a denial-of-service attack due to unsynchronized access to a shared map, which can lead to process termination when an attacker floods GET requests. This vulnerability primarily affects environments where pod-network access is available to unauthorized users, allowing them to exploit the issue and disrupt service. Organizations utilizing affected versions should prioritize upgrading to the patched releases to mitigate the risk of service interruptions.
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
Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. Prior to 1.7.4 and 1.8.1, HTTPServer.ServeHTTP in internal/wasm/httpserver.go reads the plain mappingPath2Cache map without synchronization while HTTPServer.Get writes the same map during EnvoyExtensionPolicy translation. An attacker with pod-network access to unauthenticated port 18002 and tenant permission to churn policies with distinct Wasm URLs can flood GET requests until a per-request reader overlaps a writer. Go's concurrent map read and write detection invokes runtime.throw, which the net/http connection recovery cannot catch, terminating the controller process and causing a timing-dependent, cross-tenant control-plane denial of service until Kubernetes restarts the pod. This issue is fixed in versions 1.7.4 and 1.8.1.