You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an attacker is able to flood the network with pairs of HEADERS/RST_STREAM frames, such that the h2 application is not able to accept them faster than the bytes are received, the pending accept queue can grow in memory usage. Being able to do this consistently can result in excessive memory use, and eventually trigger Out Of Memory.
This flaw is corrected in hyperium/h2#668, which restricts remote reset stream count by default.
We should try to port to latest h2 rather than point to my branch with has a patch for gRPC interop between gRPC go and Rust. Previously, we experienced a headers error when Akri's device plugins communicated with the device plugin manager in the kubelet over gRPC. That patch should now be in gRPC go
Issue has been automatically marked as stale due to inactivity for 90 days. Update the issue to remove label, otherwise it will be automatically closed.
Issue has been automatically marked as stale due to inactivity for 90 days. Update the issue to remove label, otherwise it will be automatically closed.
h2
0.2.7
>=0.3.17
If an attacker is able to flood the network with pairs of
HEADERS
/RST_STREAM
frames, such that theh2
application is not able to accept them faster than the bytes are received, the pending accept queue can grow in memory usage. Being able to do this consistently can result in excessive memory use, and eventually trigger Out Of Memory.This flaw is corrected in hyperium/h2#668, which restricts remote reset stream count by default.
See advisory page for additional details.
The text was updated successfully, but these errors were encountered: