Описание
gRPC-Go: Heap Memory Exhaustion (OOM) via HTTP/2 DATA Frame Fragmentation
Обновления
| Продукт | Статья | Обновление |
|---|---|---|
| azl3 docker-cli 25.0.7-4 on Azure Linux 3.0 | ||
| azl3 flannel 0.24.2-29 on Azure Linux 3.0 | ||
| azl3 kubevirt 1.7.1-8 on Azure Linux 3.0 | ||
| azl3 packer 1.9.5-18 on Azure Linux 3.0 | ||
| azl3 prometheus-adapter 0.12.0-7 on Azure Linux 3.0 | ||
| azl3 vitess 19.0.4-12 on Azure Linux 3.0 | ||
| azl3 containerd2 2.2.4-8 on Azure Linux 3.0 | ||
| azl3 azcopy 10.25.1-7 on Azure Linux 3.0 | ||
| azl3 azurelinux-image-tools 1.6.0-1 on Azure Linux 3.0 | ||
| azl3 cert-manager 1.12.15-11 on Azure Linux 3.0 |
Показывать по
EPSS
4.4 Medium
CVSS3
Связанные уязвимости
gRPC-Go is the Go language implementation of gRPC. Prior to 1.83.1, internal/transport/transport.go stores each fragmented HTTP/2 DATA frame as a separate recvMsg in recvBuffer, so millions of one-byte frames can consume disproportionate heap memory even when payload bytes remain within connection and stream flow-control windows. An unauthenticated remote attacker can use concurrent multiplexed streams to exhaust process memory and cause a runtime panic or out-of-memory termination. Receive-buffer compaction is enabled by default and can be controlled temporarily with GRPC_GO_EXPERIMENTAL_ENABLE_RECEIVE_BUFFER_COMPACTION. This issue is fixed in version 1.83.1.
gRPC-Go is the Go language implementation of gRPC. Prior to 1.83.1, internal/transport/transport.go stores each fragmented HTTP/2 DATA frame as a separate recvMsg in recvBuffer, so millions of one-byte frames can consume disproportionate heap memory even when payload bytes remain within connection and stream flow-control windows. An unauthenticated remote attacker can use concurrent multiplexed streams to exhaust process memory and cause a runtime panic or out-of-memory termination. Receive-buffer compaction is enabled by default and can be controlled temporarily with GRPC_GO_EXPERIMENTAL_ENABLE_RECEIVE_BUFFER_COMPACTION. This issue is fixed in version 1.83.1.
gRPC-Go is the Go language implementation of gRPC. Prior to 1.83.1, internal/transport/transport.go stores each fragmented HTTP/2 DATA frame as a separate recvMsg in recvBuffer, so millions of one-byte frames can consume disproportionate heap memory even when payload bytes remain within connection and stream flow-control windows. An unauthenticated remote attacker can use concurrent multiplexed streams to exhaust process memory and cause a runtime panic or out-of-memory termination. Receive-buffer compaction is enabled by default and can be controlled temporarily with GRPC_GO_EXPERIMENTAL_ENABLE_RECEIVE_BUFFER_COMPACTION. This issue is fixed in version 1.83.1.
gRPC-Go is the Go language implementation of gRPC. Prior to 1.83.1, in ...
EPSS
4.4 Medium
CVSS3