Memory corruption in array-tools

published 2020-12-31 5y ago modified 2026-06-17 4mo ago also GHSA-6wp2-fw3v-mfmc , RUSTSEC-2020-0132 , EUVD-2021-1607

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits: 0; none known

An issue was discovered in the array-tools crate before 0.3.2 for Rust. FixedCapacityDequeLike::clone() has a drop of uninitialized memory.

Patch / fix

fixed in 2

crates.io array-tools 0.3.2
array-tools_project array-tools 0.3.2

Is CVE-2020-36452 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.12% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
crates.io	array-tools	<0.3.2 >=0.0.0-0, <0.3.2	0.3.2

Classification

Weakness

CWE-908 Use of Uninitialized Resource
CWE-909 Missing Initialization of Resource

References

rustsec.org /advisories/RUSTSEC-2020-0132.html
web, vendor-advisory, advisory
raw.githubusercontent.com /rustsec/advisory-db/main/crates/array-tools/RUSTSEC-2020-0132.md
web, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2020-36452
advisory
github.com /L117/array-tools/issues/2
web, report
github.com /L117/array-tools
package
crates.io /crates/array-tools
package

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.