# CVE-2020-36452: Memory corruption in array-tools

> A memory corruption vulnerability in the Rust array-tools crate allows attackers to cause crashes or potentially execute code via uninitialized memory drops.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6wp2-fw3v-mfmc, RUSTSEC-2020-0132

## What is CVE-2020-36452?

CVE-2020-36452 is a critical memory corruption vulnerability in n/a, published on 8 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-908 (Use of Uninitialized Resource)

## Which versions are affected by CVE-2020-36452?

3 open source packages ship an affected version, including array-tools. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `array-tools` | crates.io | All versions | 0.3.2 |
| `array-tools` | crates.io | All versions | 0.3.2 |
| `array-tools` | crates.io | From 0.0.0-0 | 0.3.2 |

Products: Array-Tools Project Array-Tools.

## How do I fix CVE-2020-36452?

Upgrade array-tools to 0.3.2 or later.

## Is CVE-2020-36452 being exploited?

There is no known exploitation of CVE-2020-36452 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36452 and fix it if it is affected.

What it is: CVE-2020-36452 is a critical memory corruption vulnerability in n/a, published on 8 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36452 in the wild and no public exploit code.

Affected packages and fixed versions:
- array-tools (crates.io): affected all versions; fixed in 0.3.2
- array-tools (crates.io): affected all versions; fixed in 0.3.2
- array-tools (crates.io): affected from 0.0.0-0; fixed in 0.3.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-36452/ (Markdown: https://insights.sbomify.com/CVE-2020-36452/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-36452
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-36452
- OSV: https://osv.dev/vulnerability/CVE-2020-36452

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-36452/
Summaries are generated and may contain mistakes; the official description above is the record.