Skip to content
Fencer Intel
medium —

GHSA-8r5v-vm4m-4g25 json

Resource exhaustion vulnerability in h2 may lead to Denial of Service (DoS)

published 2y ago modified 2mo ago also RUSTSEC-2024-0003

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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](https://github.com/hyperium/h2/pull/737), which limits the total number of internal error resets emitted by default before the connection is closed.

Patch / fix

  • crates.io h2 0.3.24, 0.4.2

Is GHSA-8r5v-vm4m-4g25 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io h2
<0.3.24
>=0.4.0, <0.4.2
>=0.0.0-0, <0.3.24
>=0.4.0-0, <0.4.2
0.3.24
0.4.2

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.