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

gRPC-Go is the Go language implementation of gRPC. Prior to 1.82.2 and 1.83.2, servers created with xds.NewGRPCServer() allow internal/transport/http2_server.go to accept an RPC containing neither the :authority header nor the Host header, while RouteAndProcess in internal/xds/server/routing.go assumes that an authority value exists and indexes the empty slice. A remote client that can complete transport connection establishment can trigger an index-out-of-bounds panic that is not recovered by the per-RPC goroutine and terminates the entire server process. In insecure or ordinary TLS deployments the request can be unauthenticated, while strict mTLS or ALTS deployments require valid transport credentials before the malformed RPC can reach the interceptor. This issue is fixed in versions 1.82.2 and 1.83.2.

• https://github.com/grpc/grpc-go/pull/9366 x_refsource_MISC
• https://github.com/grpc/grpc-go/pull/9367 x_refsource_MISC
• https://github.com/grpc/grpc-go/security/advisories/GHSA-2v4p-qf9q-27wj x_refsource_CONFIRM
• https://github.com/grpc/grpc-go/issues/9354 x_refsource_MISC
• https://github.com/grpc/grpc-go/pull/9365 x_refsource_MISC
• https://github.com/grpc/grpc-go/commit/3822494d8ea03b992c089fd2a195f041762fffb7 x_refsource_MISC
• https://github.com/grpc/grpc-go/commit/8668b69c167df908b6b3666dcbf40992b9e932a4 x_refsource_MISC
• https://github.com/grpc/grpc-go/commit/93e31b48545e2a8aaeb6e06b47fb249f94e6297f x_refsource_MISC
• https://github.com/grpc/grpc-go/releases/tag/v1.82.2 x_refsource_MISC
• https://github.com/grpc/grpc-go/releases/tag/v1.83.2 x_refsource_MISC