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

GHSA-rpcm-whqc-jfw8

CRITICALFix: sile/libflate#37

GHSA-rpcm-whqc-jfw8 is a critical-severity (CVSS 9.8) Use After Free vulnerability in libflate. O3 Security confirms whether GHSA-rpcm-whqc-jfw8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Use after free in libflate

Also known asCVE-2019-15552RUSTSEC-2019-0010
Published
Aug 25, 2021
Updated
Nov 8, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🦀libflate

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

An issue was discovered in the libflate crate before 0.1.25 for Rust. MultiDecoder::read has a use-after-free, leading to arbitrary code execution.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.iolibflate0.1.14&&< 0.1.250.1.25

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libflate. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update libflate to 0.1.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rpcm-whqc-jfw8 is resolved across your whole dependency graph.

  3. Workarounds

    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 pinpoints whether GHSA-rpcm-whqc-jfw8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Frequently Asked Questions

An issue was discovered in the libflate crate before 0.1.25 for Rust. MultiDecoder::read has a use-after-free, leading to arbitrary code execution.
O3 Security · Impact-Aware SCA

Is GHSA-rpcm-whqc-jfw8 in your dependencies?

O3 detects GHSA-rpcm-whqc-jfw8 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-rpcm-whqc-jfw8: Use after free in… | O3 Security