# CVE-2020-36207: Data races in aovec

> A data race in the aovec crate allows memory corruption, potentially leading to code execution or denial of service.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g489-xrw3-3v8w, RUSTSEC-2020-0099

## What is CVE-2020-36207?

CVE-2020-36207 is a high-severity vulnerability in n/a, published on 22 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in the aovec crate through 2020-12-10 for Rust. Because Aovec<T> does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur.

Weakness: CWE-787 (Out-of-bounds Write), CWE-662 (Improper Synchronization)

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

3 open source packages ship an affected version, including aovec. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aovec` | crates.io | All versions to 1.1.0 | None |
| `aovec` | crates.io | All versions to 1.1.0 | None |
| `aovec` | crates.io | From 0.0.0-0 | None |

Products: Aovec Project Aovec.

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

No fix has been published for CVE-2020-36207 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-36207 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36207 is a high-severity vulnerability in n/a, published on 22 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36207 in the wild and no public exploit code.

Affected packages and fixed versions:
- aovec (crates.io): affected all versions up to 1.1.0; no fix listed
- aovec (crates.io): affected all versions up to 1.1.0; no fix listed
- aovec (crates.io): affected from 0.0.0-0; no fix listed

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-36207/ (Markdown: https://insights.sbomify.com/CVE-2020-36207/index.md)
```

## Sources

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

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