dbcve.org
Id MapApplication · Id Map Project

CVE-2021-30455

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 IdMap::clone_from upon a .clone panic.

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 IdMap::clone_from method. When cloning map entries and a .clone() call panics, the method fails to properly manage ownership, leading to a double-free condition. This is a memory safety issue in unsafe Rust code where resource cleanup is mishandled during panic propagation.

MitigationUpdate the id-map crate to a version that addresses this vulnerability. Ensure that any custom types stored in the map have panic-safe clone implementations, or consider using types that implement panic-safe cloning traits.

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. Identify id-map crate in dependency tree
    Search your Cargo.lock file or Cargo.toml for 'id-map' or 'id_map' crate references
    Affected if The id-map crate is present in your project dependencies
  2. Determine id-map version
    Locate the version entry in Cargo.lock under [[package]] name="id-map" - versions are date-based (e.g., 2021-02-26)
    Affected if Version is 2021-02-26 or earlier
  3. Find IdMap cloning operations
    Search source code for IdMap::clone_from method calls or .clone() usage on IdMap instances
    Affected if Code performs cloning operations on IdMap containers
  4. Evaluate stored type panic safety
    Review the generic types stored in IdMap and determine if their Clone implementations can panic
    Affected if Types stored in the map may panic when .clone() is invoked

You are affected if you depend on id-map version 2021-02-26 or earlier AND use cloning operations on IdMap with types that could panic during clone.

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 the id-map crate to a version that addresses this vulnerability. Ensure that any custom types stored in the map have panic-safe clone implementations, or consider using types that implement panic-safe cloning traits.

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-30455 — 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-30455 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