Summary
Envoy Gateway can expose its xDS gRPC services without effective JWT authentication in certain GatewayNamespaceMode deployments. A pod that can reach the xDS server may retrieve sensitive gateway data, including TLS private keys, routing configuration, xDS resources, and backend endpoint information.
Affected context
The issue occurs in Envoy Gateway deployments using the Kubernetes GatewayNamespace provider mode and the xDS gRPC server. The affected configuration installs authentication for streaming requests but does not consistently protect unary requests or State-of-the-World discovery requests, allowing some resource-retrieval paths to proceed without JWT validation.
Exploit preconditions
- Attack surface: The Envoy Gateway xDS gRPC server, including its configured service port
- Required access: Network reachability from a pod or other environment with access to the xDS endpoint
- Trigger point: Unary Fetch RPCs or streaming RPCs using State-of-the-World discovery requests
- Why exploitation is possible: Authentication coverage is incomplete, and the interceptor does not validate all supported discovery request types
Why this happens
The underlying defect is missing authentication enforcement on security-sensitive gRPC methods, mapping to CWE-306: Missing Authentication for Critical Function. The server registers a JWT interceptor for streaming operations but omits equivalent protection for unary operations. In addition, authentication logic recognizes only DeltaDiscoveryRequest messages, allowing State-of-the-World DiscoveryRequest messages to bypass validation because the request type is not handled by the interceptor.
Potential impact
- Unauthorized parties may retrieve TLS private keys
- Attackers could obtain xDS resources and gateway configuration
- Backend service endpoints may be disclosed
- Routing and listener configuration could be exposed
- The disclosed information could support lateral movement or targeted attacks
General mitigation guidance
Mitigation generally focuses on enforcing authentication consistently across every xDS RPC shape and supported discovery protocol.
Common defensive patterns include:
- Apply JWT or equivalent authentication to both unary and streaming RPCs
- Validate every supported discovery request type before processing it
- Prefer deny-by-default behavior when request types are unknown or unsupported
- Restrict network access to the xDS endpoint using namespace, pod, network, and service-boundary controls
- Run gateway components with only the permissions required for their roles
- Treat TLS private keys and control-plane resources as highly sensitive data
How teams detect issues like this
Organizations can assess this risk through:
- Static and configuration analysis that checks authentication coverage for every registered gRPC method
- Code review for interceptors that omit unary handlers or recognize only one protocol message type
- Integration tests covering both unary and streaming RPCs, including Delta and State-of-the-World discovery flows
- Network policy reviews verifying that only authorized gateway components can reach the xDS port
- Runtime monitoring for unexpected requests to secret, route, cluster, listener, or endpoint discovery services
- Automated security review tools that identify missing authorization paths and fail-open request handling

