Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
An attacker can cause excessive memory growth in a Go server accepting HTTP/2 requests. HTTP/2 server connections contain a cache of HTTP header keys sent by the client. While the total number of entries in this cache is capped, an attacker sending very large keys can cause the server to allocate approximately 64 MiB per open connection.
Recommended action: Upgrade to 0.4.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go golang.org/x/net/http2 < 0.0.0-20220906165146-f3363e06e74c
Fixed in
0.0.0-20220906165146-f3363e06e74c· Vendor fix available
Issue
In net/http in Go before 1.18.6 and 1.19.x before 1.19.1, attackers can cause a denial of service because an HTTP/2 connection can hang during closing if shutdown were preempted by a fatal error.
Recommended action: Upgrade to 0.0.0-20220906165146-f3363e06e74c (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go golang.org/x/net/http2 < 0.0.0-20211209124913-491a49abca63
Fixed in
0.0.0-20211209124913-491a49abca63· Vendor fix available
Issue
net/http in Go before 1.16.12 and 1.17.x before 1.17.5 allows uncontrolled memory consumption in the header canonicalization cache via HTTP/2 requests.
Recommended action: Upgrade to 0.0.0-20211209124913-491a49abca63 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.