Read the docs
TI-2024-38551 Aliases GHSA-w7hm-hmxv-pvhf

HPACK decoder panics on invalid input

Priority LOW 38CWE-754Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
No fix listed

No CVSS vector from any source. Fix status from GitHub.

Summary

Due to insufficient checking of input data, decoding certain data sequences can lead to _Decoder::decode_ panicking rather than returning an error. Example code that triggers this vulnerability looks like this: ```rust use hpack::Decoder; pub fn main() { let input = &[0x3f]; let mut decoder = Decoder::new(); let _ = decoder.decode(input); } ``` hpack is unmaintained. A crate with the panics fixed has been published as [hpack-patched](https://crates.io/crates/hpack-patched). Also consider using [fluke-hpack](https://crates.io/crates/fluke-hpack) or [httlib-huffman](https://crates.io/crates/httlib-huffman) as an alternative.

Why it matters now

Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—hpack (crates.io)up to 0.3.0—No fix listedGHSA-w7hm-hmxv-pvhf
  • hpack (crates.io) Vendor— Affected up to 0.3.0 Fixed in — No fix listed GHSA-w7hm-hmxv-pvhf

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-03 Threatist record created from GHSA-w7hm-hmxv-pvhf

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences