# CVE-2021-30457: Double-free in id-map

> A double free vulnerability in the Rust id-map crate allows attackers to cause denial of service or potentially execute code via a panic in a Drop implementation.

- **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:** No
- **Published:** 7 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rccq-j2m7-8fwr

## What is CVE-2021-30457?

CVE-2021-30457 is a critical use after free vulnerability in n/a, published on 7 Apr 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 id-map crate through 2021-02-26 for Rust. A double free can occur in remove_set upon a panic in a Drop impl.

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2021-30457?

2 open source packages ship an affected version, including id-map. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `id-map` | crates.io | All versions to 0.2.1 | None |
| `id-map` | crates.io | All versions to 0.2.1 | None |

Products: Id-Map Project Id-Map.

## How do I fix CVE-2021-30457?

No fix has been published for CVE-2021-30457 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-30457 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-30455](https://insights.sbomify.com/CVE-2021-30455/): Double-free in id-map (critical 9.8)
- [CVE-2021-30456](https://insights.sbomify.com/CVE-2021-30456/): Double-free in id-map (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-30457 and fix it if it is affected.

What it is: CVE-2021-30457 is a critical use after free vulnerability in n/a, published on 7 Apr 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-2021-30457 in the wild and no public exploit code.

Affected packages and fixed versions:
- id-map (crates.io): affected all versions up to 0.2.1; no fix listed
- id-map (crates.io): affected all versions up to 0.2.1; no fix listed

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

## Sources

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

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