Description
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.
Remediation
References
Related Vulnerabilities
WordPress Plugin Travelpayouts:All Travel Brands in One Place Cross-Site Request Forgery (1.0.16)
MySQL Use of Externally-Controlled Format String Vulnerability (CVE-2006-3469)
WordPress Plugin Jammer Cross-Site Scripting (0.2)
Sqlite Integer Overflow or Wraparound Vulnerability (CVE-2018-20346)
XWikiplatform Missing Authorization Vulnerability (CVE-2024-31983)