Memory corruption in array-tools
An issue was discovered in the array-tools crate before 0.3.2 for Rust. Affected versions of this crate don't guard against panics, so that partially uninitialized buffer is dropped when user-provided `T::clone()` panics in `FixedCapacityDequeLike<T, A>::clone()`. This causes memory corruption.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-36452US | critical9.8 | — | ||
An issue was discovered in the array-tools crate before 0.3.2 for Rust. FixedCapacityDequeLike::clone() has a drop of uninitialized memory. | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/L117/array-toolsPACKAGE
- https://github.com/L117/array-tools/issues/2WEB
- https://nvd.nist.gov/vuln/detail/CVE-2020-36452ADVISORY
- https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/array-tools/RUSTSEC-2020-0132.mdWEB
- https://rustsec.org/advisories/RUSTSEC-2020-0132.htmlWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan