Описание
gRPC-Go: Denial of Service (DoS) via crash due to missing :authority and Host headers in the xDS servers
Обновления
| Продукт | Статья | Обновление |
|---|---|---|
| azl3 azcopy 10.25.1-8 on Azure Linux 3.0 | ||
| azl3 azurelinux-image-tools 1.6.0-2 on Azure Linux 3.0 | ||
| azl3 cert-manager 1.12.15-12 on Azure Linux 3.0 | ||
| azl3 cf-cli 8.7.11-8 on Azure Linux 3.0 | ||
| azl3 containerd2 2.2.4-8 on Azure Linux 3.0 | ||
| azl3 cri-tools 1.32.0-7 on Azure Linux 3.0 | ||
| azl3 docker-buildx 0.14.0-16 on Azure Linux 3.0 | ||
| azl3 docker-compose 2.27.0-13 on Azure Linux 3.0 | ||
| azl3 flannel 0.24.2-31 on Azure Linux 3.0 | ||
| azl3 keda 2.14.1-18 on Azure Linux 3.0 |
Показывать по
EPSS
Связанные уязвимости
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.
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.
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.
gRPC-Go is the Go language implementation of gRPC. Prior to 1.82.2 and ...
EPSS