Rust advisories / arr
Vulnerability CriticalRUSTSEC-2020-0034 · arr
RUSTSEC-2020-0034: Multiple security issues including data race, buffer overflow, and uninitialized memory drop
Short answerA security vulnerability in the arr crate: Multiple security issues including data race, buffer overflow, and uninitialized memory drop. GitHub rates it Critical. No fixed version: replace the crate or remove the affected code path.
| Crate | arr |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | Critical (GitHub rating) |
| Published | 2020-08-25 |
| Last changed | 2024-03-15 |
| Also known as | CVE-2020-35886, CVE-2020-35887, CVE-2020-35888, GHSA-36xw-hgfv-jwm7, GHSA-c7fw-cr3w-wvfc, GHSA-fhvj-7f9p-w788 |
What to do
- Find who pulls it in:
cargo tree -i arr. - Avoid the affected API, or replace the crate.
Details from the advisory
arr crate contains multiple security issues. Specifically,
1. It incorrectly implements Sync/Send bounds, which allows to smuggle non-Sync/Send types across the thread boundary. 2. Index and IndexMut implementation does not check the array bound. 3. Array::new_from_template() drops uninitialized memory.
References
- Package: crates.io/crates/arr
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0034.html
- Report: github.com/sjep/array/issues/1
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?