HTTP/2 CONTINUATION flood in net/http
An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.
Updated 6.1 container image is now available in the Red Hat Ecosystem Catalog.
Released 2025-04-28 · Red Hat rating Important · View on Red Hat →
An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.
The archive/zip package's handling of certain types of invalid zip files differs from the behavior of most zip implementations.
The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms.
Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.
A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption.
A malformed DNS message in response to a query can cause the Lookup functions to get stuck in an infinite loop.