Rust advisories / aovec
Vulnerability HighRUSTSEC-2020-0099 · aovec
RUSTSEC-2020-0099: Aovec<T> lacks bound on its Send and Sync traits allowing data races
Short answerA security vulnerability in the aovec crate: Aovec<T> lacks bound on its Send and Sync traits allowing data races. High severity (CVSS 7.0). No fixed version: replace the crate or remove the affected code path.
| Crate | aovec |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | High, CVSS 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| Published | 2020-12-10 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36207, GHSA-g489-xrw3-3v8w |
What to do
- Find who pulls it in:
cargo tree -i aovec. - Avoid the affected API, or replace the crate.
Details from the advisory
aovec::Aovec<T> is a vector type that implements Send and Sync for all types T.
This allows non-Send types such as Rc and non-Sync types such as Cell to be used across thread boundaries which can trigger undefined behavior and memory corruption.
References
- Package: crates.io/crates/aovec
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0099.html
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?