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.
golang.org/x/net/http2
{
"nvd_published_at": "2019-08-13T21:15:00Z",
"severity": "HIGH",
"github_reviewed_at": "2023-02-08T00:30:13Z",
"github_reviewed": true,
"cwe_ids": [
"CWE-400"
]
}