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.
{
"versions": [
{
"introduced": "6.0.0"
},
{
"last_affected": "6.2.3"
},
{
"introduced": "7.0.0"
},
{
"last_affected": "7.1.6"
},
{
"introduced": "8.0.0"
},
{
"last_affected": "8.0.3"
},
{
"introduced": "0"
},
{
"last_affected": "10.0"
}
]
}{
"versions": [
{
"introduced": "1.0.0"
},
{
"last_affected": "1.4.0"
}
]
}{
"versions": [
{
"introduced": "8.0.0"
},
{
"last_affected": "8.8.1"
},
{
"introduced": "8.9.0"
},
{
"fixed": "8.16.1"
},
{
"introduced": "10.0.0"
},
{
"last_affected": "10.12.0"
},
{
"introduced": "10.13.0"
},
{
"fixed": "10.16.3"
},
{
"introduced": "12.0.0"
},
{
"fixed": "12.8.1"
}
]
}