Some HTTP/2 implementations are vulnerable to ping floods, 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 ping floods, potentially leading to a denial of service. The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.
From the CVE record · certcc
Affected HTTP/2 implementations can build up an internal queue of responses to continual pings. An attacker able to send pings to an HTTP/2 peer can consume excess CPU, memory, or both, potentially causing a denial of service. The input does not specify whether authentication is required.
Engineers using golang.org/x/net before 0.0.0-20190813141303-74dc4d7220e7 or Go stdlib before 1.11.13 or from 1.12.0-0 through versions before 1.12.8 should check their deployments.