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
4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
The h2 crate, used internally by hyper, had a flaw that would accept and queue empty DATA frames without limit. If streams were not actively drained, this could lead to unbounded memory usage, or a panic if the length overflows. Low severity. Patched in v0.4.16.
Recommended action: Upgrade to 0.4.16 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
An attacker can send a flood of CONTINUATION frames, causing h2 to process them indefinitely. This results in an increase in CPU usage. Tokio task budget helps prevent this from a complete denial-of-service, as the server can still respond to legitimate requests, albeit with increased latency. More details at https://seanmonstar.com/blog/hyper-http2-continuation-flood/. Patches available for 0.4.x and 0.3.x versions.
Recommended action: Upgrade to 0.4.4 or 0.3.26 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
An attacker with an HTTP/2 connection to an affected endpoint can send a steady stream of invalid frames to force the generation of reset frames on the victim endpoint. By closing their recv window, the attacker could then force these resets to be queued in an unbounded fashion, resulting in Out Of Memory (OOM) and high CPU usage. This fix is corrected in hyperium/h2#737, which limits the total number of internal error resets emitted by default before the connection is closed.
Recommended action: Upgrade to 0.4.2 or 0.3.24 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Hyper is an HTTP library for Rust and h2 is an HTTP 2.0 client & server implementation for Rust. An issue was discovered in h2 v0.2.4 when processing header frames. It incorrectly processes the HTTP2 RSTSTREAM frames by not always releasing the memory immediately upon receiving the reset frame, leading to stream stacking. As a result, the memory and CPU usage are high which can lead to a Denial of Service (DoS). This issue affects users only when dealing with http2 connections.
Recommended action: Upgrade to 0.3.17 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.