جزئیات آسیب‌پذیری

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, the xDS gRPC server in GatewayNamespaceMode, configured through provider.kubernetes.deploy.type=GatewayNamespace, installs a JWT StreamInterceptor but no UnaryInterceptor, leaving every unary Fetch RPC unauthenticated. The streaming interceptor also authenticates only discoveryv3.DeltaDiscoveryRequest messages; a discoveryv3.DiscoveryRequest used by the State-of-the-World protocol fails the type assertion and returns success without JWT validation. Any pod that can reach port 18000 can use the unauthenticated unary or State-of-the-World paths to retrieve TLS private keys through StreamSecrets, all xDS resources through StreamAggregatedResources, backend endpoints through StreamClusters or StreamEndpoints, and routing configuration through StreamRoutes or StreamListeners. This issue is fixed in versions 1.7.4 and 1.8.1.

• https://github.com/envoyproxy/gateway/pull/9118 x_refsource_MISC
• https://github.com/envoyproxy/gateway/security/advisories/GHSA-22xc-xg2r-9j7v x_refsource_CONFIRM
• https://github.com/envoyproxy/gateway/pull/8986 x_refsource_MISC
• https://github.com/envoyproxy/gateway/pull/9116 x_refsource_MISC
• https://github.com/envoyproxy/gateway/commit/4df0809ff1ed59ffb09604da4084335b8c6647c5 x_refsource_MISC
• https://github.com/envoyproxy/gateway/commit/e9124abc4ff4b63a218a6890c1b28a982c850465 x_refsource_MISC
• https://github.com/envoyproxy/gateway/commit/f1f9829af2a231f0cae915c09800353c76622d97 x_refsource_MISC
• https://github.com/envoyproxy/gateway/releases/tag/v1.7.4 x_refsource_MISC
• https://github.com/envoyproxy/gateway/releases/tag/v1.8.1 x_refsource_MISC