# CVE-2020-36212: Memory corruption in n/a

> A double drop vulnerability in the abi_stable crate's DrainFilter allows attackers to cause memory corruption, potentially leading to code execution or crashes.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 22 Jan 2021
- **Updated:** 4 Aug 2024

## What is CVE-2020-36212?

CVE-2020-36212 is a high-severity memory corruption vulnerability in n/a, published on 22 Jan 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 abi_stable crate before 0.9.1 for Rust. DrainFilter lacks soundness because of a double drop.

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

It affects 1 product.


Products: Abi Stable Project Abi Stable.

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

Upgrade to a fixed version.

## Is CVE-2020-36212 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-36213](https://insights.sbomify.com/CVE-2020-36213/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36212 is a high-severity memory corruption vulnerability in n/a, published on 22 Jan 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-36212 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-36212/ (Markdown: https://insights.sbomify.com/CVE-2020-36212/index.md)
```

## Sources

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

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