Vulnerability MediumRUSTSEC-2024-0400 · ruzstd
RUSTSEC-2024-0400: `ruzstd` uninit and out-of-bounds memory reads
Short answerA security vulnerability in the ruzstd crate: `ruzstd` uninit and out-of-bounds memory reads. GitHub rates it Medium. Fixed in 0.7.3: update to a fixed version.
| Crate | ruzstd |
|---|---|
| Type | Vulnerability (memory-exposure) |
| Affected versions | From 0.7.0 before 0.7.3. |
| Fixed in | 0.7.3 |
| Severity | Medium (GitHub rating) |
| Published | 2024-11-28 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-x3f4-45xf-rjm7 |
What to do
- See which version you have:
cargo tree -i ruzstd(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p ruzstd. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleruzstd = "0.7.3") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
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 copy_bytes_overshooting 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.
References
- Package: crates.io/crates/ruzstd
- Advisory: rustsec.org/advisories/RUSTSEC-2024-0400.html
- Report: github.com/KillingSpark/zstd-rs/issues/75
- Web: github.com/KillingSpark/zstd-rs/pull/76
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for ruzstd
Up next
Same crateruzstd: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?