Rust advisories / rmpv
Vulnerability MediumRUSTSEC-2017-0006 · rmpv
RUSTSEC-2017-0006: Unchecked vector pre-allocation
Short answerA security vulnerability in the rmpv crate: Unchecked vector pre-allocation. GitHub rates it Medium. Fixed in 0.4.2: update to a fixed version.
| Crate | rmpv |
|---|---|
| Type | Vulnerability (denial-of-service) |
| Affected versions | Before 0.4.2. |
| Fixed in | 0.4.2 |
| Severity | Medium (GitHub rating) |
| Published | 2017-11-21 |
| Last changed | 2023-11-08 |
| Also known as | GHSA-mcrf-7hf9-f6q5 |
What to do
- See which version you have:
cargo tree -i rmpv(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p rmpv. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplermpv = "0.4.2") 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 this crate pre-allocate memory on deserializing raw buffers without checking whether there is sufficient data available.
This allows an attacker to do denial-of-service attacks by sending small msgpack messages that allocate gigabytes of memory.
References
- Package: crates.io/crates/rmpv
- Advisory: rustsec.org/advisories/RUSTSEC-2017-0006.html
- Report: github.com/3Hren/msgpack-rust/issues/151
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?