Envoy Gateway: Wasm cache ServeHTTP reads mappingPath2Cache without lock
13Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 5.3epss 0.4%
probabilidad de explotación
0.4%top 70% de las CVE
explotación observada
noninguna fuente lo reporta
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.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Productos afectados
envoyproxy · gatewayReferencias
https://github.com/envoyproxy/gateway/commit/5a78db82b7cf4fc5bebbeda2c50952892038a464https://github.com/envoyproxy/gateway/commit/96e2b750868a459ace4b8b68e6a6e4fb0152b9b7https://github.com/envoyproxy/gateway/commit/b4737180c7e597490c6363075c565fa8cf24eeadhttps://github.com/envoyproxy/gateway/pull/9171https://github.com/envoyproxy/gateway/pull/9172https://github.com/envoyproxy/gateway/pull/9173https://github.com/envoyproxy/gateway/releases/tag/v1.7.4https://github.com/envoyproxy/gateway/releases/tag/v1.8.1https://github.com/envoyproxy/gateway/security/advisories/GHSA-8fv2-88gg-hm7q