published 13 Aug 2019 · updated 4 Aug 2024
Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service
8.5HighCVSS 7.5EPSS 88%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 88%. No fixed version is recorded.
Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket