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: use hpack::Decoder; pub fn main() { let input = &[0x3f]; let mut decode...
Product
crates.io hpack vulnerabilities
2 published CVES affecting crates.io hpack, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 2
- Critical
- 0
- High
- 1
- Medium
- 0
- Low
- 0
- Unscored
- 1
- CISA KEV
- 0
Latest crates.io hpack CVEs
Newest publication first
-
HighCVSS 7.5
-
Unknown
The hpack crate is no longer maintained. Consider using fluke-hpack or httlib-huffman.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.