Vulnerability HighRUSTSEC-2020-0157 · vm-memory
RUSTSEC-2020-0157: Improper Synchronization and Race Condition in vm-memory
Short answerA security vulnerability in the vm-memory crate: Improper Synchronization and Race Condition in vm-memory. High severity (CVSS 7.5). Fixed in 0.1.1, 0.2.1: update to a fixed version.
| Crate | vm-memory |
|---|---|
| Type | Vulnerability (memory-corruption) |
| Affected versions | Before 0.1.1; from 0.2.0 before 0.2.1. |
| Fixed in | 0.1.1, 0.2.1 |
| Severity | High, CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| Published | 2020-06-02 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-13759, GHSA-mm4m-qg48-f7wc |
What to do
- See which version you have:
cargo tree -i vm-memory(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p vm-memory. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplevm-memory = "0.2.1") 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
rust-vmm vm-memory before 0.1.1 and 0.2.x before 0.2.1 allows attackers to cause a denial of service (loss of IP networking) because read_obj and write_obj do not properly access memory. This affects aarch64 (with musl or glibc) and x86_64 (with musl).
References
- Package: crates.io/crates/vm-memory
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0157.html
- Web: nvd.nist.gov/vuln/detail/CVE-2020-13759
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 vm-memory
Up next
Same cratevm-memory: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?