# CVE-2020-13759: Improper Synchronization and Race Condition in vm-memory

> Attackers can cause denial of service by exploiting improper memory access in the rust-vmm vm-memory library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mm4m-qg48-f7wc, RUSTSEC-2020-0157

## What is CVE-2020-13759?

CVE-2020-13759 is a high-severity vulnerability in n/a, published on 2 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-662 (Improper Synchronization), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2020-13759?

5 open source packages ship an affected version, including vm-memory. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vm-memory` | crates.io | All versions | 0.1.1 |
| `vm-memory` | crates.io | All versions | 0.1.1 |
| `vm-memory` | crates.io | From 0.0.0-0 | 0.1.1, 0.2.1 |
| `vm-memory` | crates.io | From 0.2.0 | 0.2.1 |
| `vm-memory` | crates.io | From 0.2.0 | 0.2.1 |

Products: Vm-Memory Project Vm-Memory.

## How do I fix CVE-2020-13759?

Upgrade vm-memory to a fixed version for your release line: 0.1.1 or 0.2.1.

## Is CVE-2020-13759 being exploited?

There is no known exploitation of CVE-2020-13759 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-41051](https://insights.sbomify.com/CVE-2023-41051/): Default functions in VolatileMemory trait lack bounds checks in vm-memory (low 2.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-13759 and fix it if it is affected.

What it is: CVE-2020-13759 is a high-severity vulnerability in n/a, published on 2 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-13759 in the wild and no public exploit code.

Affected packages and fixed versions:
- vm-memory (crates.io): affected all versions; fixed in 0.1.1
- vm-memory (crates.io): affected all versions; fixed in 0.1.1
- vm-memory (crates.io): affected from 0.0.0-0; fixed in 0.1.1, 0.2.1
- vm-memory (crates.io): affected from 0.2.0; fixed in 0.2.1
- vm-memory (crates.io): affected from 0.2.0; fixed in 0.2.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-13759/ (Markdown: https://insights.sbomify.com/CVE-2020-13759/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-13759
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-13759
- OSV: https://osv.dev/vulnerability/CVE-2020-13759

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-13759/
Summaries are generated and may contain mistakes; the official description above is the record.