Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

ruzstd

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5crates.ioPublished

    Decompression bomb in ruzstd: a tiny input can exhaust memory (OOM)

    Affected
    • crates.io ruzstd >= 0.0.0-0, < 0.9.1
    Fixed in
    0.9.1· Vendor fix available
    Issue
    A crafted `.zst` input under 128 KB can force `ruzstd` to allocate several gigabytes at once, crashing the process with an out-of-memory condition. Since `ruzstd` is a decoder for untrusted input, a single small file is enough to take down anything decoding it. The compressed size of a block was capped at 128 KB, but a compressed block's decompressed size was never checked against `Block_Maximum_Size = min(Window_Size, 128 KiB)` (RFC 8878). In `execute_sequences` the output was built with no running bound and no flush between blocks, so one block could expand to gigabytes — bypassing both the configured window-size limit and the block-by-block streaming that would otherwise release memory. (A related `u32` counter overflow on such a block caused an additional panic.) This is a denial of service only; memory access stays in bounds (no corruption, no RCE). `ruzstd` is also built as a dependency of the Rust standard library via `rustc-dep-of-std`; in the toolchain it is used only to…

    Recommended action: Upgrade to 0.9.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.devSource checked Evidence →
  2. Unratedcrates.ioPublished

    ruzstd uninit and out-of-bounds memory reads

    GHSA-x3f4-45xf-rjm7

    Affected
    • crates.io ruzstd >= 0.7.0, < 0.7.3
    Fixed in
    0.7.3· Vendor fix available
    Issue
    Affected versions of ruzstd miscalculate the length of the allocated and init section of its internal RingBuffer, leading to uninitialized or out-of-bounds reads in copybytesovershooting of up to 15 bytes. This may result in up to 15 bytes of memory contents being written into the decoded data when decompressing a crafted archive. This may occur multiple times per archive.

    Recommended action: Upgrade to 0.7.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →