Rust advisories / autorand
Vulnerability HighRUSTSEC-2020-0103 · autorand
RUSTSEC-2020-0103: `impl Random` on arrays can lead to dropping uninitialized memory
Short answerA security vulnerability in the autorand crate: `impl Random` on arrays can lead to dropping uninitialized memory. High severity (CVSS 7.8). Fixed in 0.2.3: update to a fixed version.
| Crate | autorand |
|---|---|
| Type | Vulnerability (memory-corruption) |
| Affected versions | Before 0.2.3. |
| Fixed in | 0.2.3 |
| Severity | High, CVSS 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| Published | 2020-12-31 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36210, GHSA-cgmg-2v6m-fjg7 |
What to do
- See which version you have:
cargo tree -i autorand(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p autorand. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleautorand = "0.2.3") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
Affected versions of this crate had a panic safety issue to drop partially uninitialized array of T upon panic in a user provided function T::random(). Dropping uninitialized T can potentially cause memory corruption or undefined behavior.
The flaw was corrected in commit 565d508 by using MaybeUninit<T> to avoid possible dropping of uninitialized memory upon panic.
References
- Package: crates.io/crates/autorand
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0103.html
- Report: github.com/mersinvald/autorand-rs/issues/5
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?