Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀
🦀 crates.io
Not in CISA KEV
HIGH severity

GHSA-w7hm-hmxv-pvhf — hpack

HIGHFix: sno2/hpack-rs-patched@d669282

GHSA-w7hm-hmxv-pvhf is a high-severity (CVSS 7.5) vulnerability in hpack. No vendor fix is recorded yet; mitigation options are listed below.

HPACK decoder panics on invalid input

Also known asRUSTSEC-2023-0085
Published
Apr 5, 2024
Updated
Apr 11, 2024
Affected
1 pkg
Patched
See advisory
Exploits
None indexed
Exploitation data as of Apr 11, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🦀hpack

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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 decoder = Decoder::new();
  let _ = decoder.decode(input);
}

hpack is unmaintained. A crate with the panics fixed has been published as hpack-patched.

Also consider using fluke-hpack or httlib-huffman as an alternative.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🦀crates.iohpackall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hpack, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of hpack has shipped for GHSA-w7hm-hmxv-pvhf yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w7hm-hmxv-pvhf can be triaged on real exposure rather than presence alone.

Tailored to GHSA-w7hm-hmxv-pvhf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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/
O3 Security · Impact-Aware SCA

Is GHSA-w7hm-hmxv-pvhf in your dependencies?

O3 Security finds GHSA-w7hm-hmxv-pvhf across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-w7hm-hmxv-pvhf: hpack (High 7.5) | O3 Security