Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| golang.org/x/net Go |
|
|
| stdlib Go |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| golang.org/x/net Go |
|
|
| stdlib Go |
|
|
Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service. The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both.
From the CVE record · certcc
Affected HTTP/2 implementations can consume excess memory or CPU when handling a reset flood. A remote attacker can open multiple streams and send invalid requests that trigger RST_STREAM frames, potentially causing a denial of service.
Engineers using golang.org/x/net before 0.0.0-20190813141303-74dc4d7220e7 or Go stdlib before 1.11.13 on the 1.11 line, or from 1.12.0-0 through versions before 1.12.8, should check their deployments.