Description
The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control.
Mitigation
Minimal update. May introduce new vulnerabilities or breaking changes.
|
 go | | >=0 <1.26.9 || >=1.27.0-0 <1.27.2 | 1.26.9, 1.27.2 |
go | | | 0.60.0 |
 debian 12 | | =1.19.10-1 || =1.19.10-2 || =1.19.11-1 || =1.19.12-1 || =1.19.12-2 || =1.19.12-2~bpo11+1 || =1.19.12-2~bpo12+1 || =1.19.13-1 || =1.19.13-1~bpo11+1 || =1.19.13-1~bpo12+1 || =1.19.8-2 || =1.19.9-1 | - |
debian 14 | | =1.26.0-1 || =1.26.1-1 || =1.26.2-1 || =1.26.2-2 || =1.26.2-3 || =1.26.3-1 || =1.26.3-1~bpo13+1 || =1.26.3-2 || =1.26.3-2~bpo13+1 || =1.26.4-1 || =1.26.4-1~bpo13+1 || =1.26.5-1 || =1.26.5-1~bpo13+1 || =1.26.6-1 || =1.26.6-2 || =1.26.7-1 || =1.26.7-1~bpo13+1 || =1.26.8-1 || =1.26.8-1~bpo13+1 || =1.26.8-2 || =1.26~rc2-1 || =1.26~rc3-1 || =1.26~rc3-2 || >=0 <1.26.9-1 | 1.26.9-1 |
debian 12 | | =1:0.10.0-1 || =1:0.11.0-1 || =1:0.14.0-1 || =1:0.15.0-1 || =1:0.15.0-2 || =1:0.17.0+dfsg-1 || =1:0.19.0+dfsg-1 || =1:0.20.0+dfsg-1 || =1:0.21.0+dfsg-1 || =1:0.22.0+dfsg-1 || =1:0.23.0+dfsg-1 || =1:0.24.0+dfsg-1 || =1:0.25.0+dfsg-1 || =1:0.26.0+dfsg-1 || =1:0.26.0+dfsg-2 || =1:0.27.0-1 || =1:0.27.0-2 || =1:0.47.0-1 || =1:0.47.0-2 || =1:0.53.0-1 || =1:0.53.0-2 || =1:0.53.0-2~bpo13+1 || =1:0.55.0-1 || =1:0.56.0-1 || =1:0.57.0-1 || =1:0.58.0-1 || =1:0.60.0-1 || =1:0.7.0+dfsg-1 | - |
debian 14 | | =1:0.27.0-2 || =1:0.47.0-1 || =1:0.47.0-2 || =1:0.53.0-1 || =1:0.53.0-2 || =1:0.53.0-2~bpo13+1 || =1:0.55.0-1 || =1:0.56.0-1 || =1:0.57.0-1 || =1:0.58.0-1 || >=0 <1:0.60.0-1 | 1:0.60.0-1 |
 rpm rhel8 | | - | - |
rpm rhel9 | | - | - |
rpm rhel8 | | - | - |
rpm rhel9 | | - | - |
