dbcve.org
Id MapApplication · Id Map Project

CVE-2021-30456

CRITICAL · 9.8 CVSS v3.1 Published 2021-04-07
Fix available
A fix is available. Upgrade to after 2021-02-26 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in the id-map crate through 2021-02-26 for Rust. A double free can occur in get_or_insert upon a panic of a user-provided f function.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The id-map Rust crate has a double-free vulnerability in the get_or_insert function. When a user-provided closure f panics, memory allocated for the map entry is freed twice - once during panic unwinding and again in the cleanup path, causing undefined behavior and potential code execution.

MitigationUpdate to a patched version of the id-map crate that implements proper panic handling in get_or_insert, or avoid using this function until a patched version is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Id MapApplication
Affected:<= 2021-02-26

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate id-map dependency in your project
    Search Cargo.lock for 'name = "id-map"' and note the version number listed
    Affected if The version is 2021-02-26 or earlier, or no version is specified indicating an old snapshot
  2. Identify usage of get_or_insert function
    Search your source code for calls to get_or_insert method on IdMap types
    Affected if The function is used anywhere in your codebase with a user-provided closure f
  3. Check if closures passed to get_or_insert can panic
    Review the closure code passed to get_or_insert for any operations that could panic (indexing, unwrap, expect, division, etc.)
    Affected if The closure contains any panic-inducing operations and get_or_insert is called at runtime
  4. Verify Cargo.lock timestamp or version date
    Inspect the Cargo.lock entry for id-map - if using a date-based version, check if it is on or before 2021-02-26
    Affected if The lockfile shows id-map version dated 2021-02-26 or earlier

You are affected if id-map crate version is 2021-02-26 or earlier AND your code calls get_or_insert with a closure that could potentially panic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2021-02-26
Interim mitigation

Update to a patched version of the id-map crate that implements proper panic handling in get_or_insert, or avoid using this function until a patched version is available.

Fix this in Id Map Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-30456 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-30456 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data