Id MapApplication · Id Map Project
CVE-2021-30457
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 · uneditedAn 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.
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 · moderate confidenceA double-free vulnerability exists in the id-map Rust crate's remove_set function. When a panic occurs during a Drop implementation while the data structure is being modified, the memory can be deallocated twice, leading to potential memory corruption and arbitrary code execution.
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
<= 2021-02-26CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate id-map crate dependencySearch your project's Cargo.toml and Cargo.lock files for the 'id-map' crate dependencyAffected if The id-map crate is listed as a dependency in your project
-
Identify installed id-map versionCheck the version number specified in Cargo.toml or resolved in Cargo.lock for the id-map entryAffected if The version is dated 2021-02-26 or earlier (check the date or version string against the affected release)
-
Verify remove_set function usageSearch your codebase for calls to the remove_set method on id-map data structuresAffected if Your code calls remove_set on id-map collections
-
Inspect Drop implementations for panic potentialReview any custom Drop implementations that interact with id-map collections, looking for code that could panic (unwrap, expect, indexing operations, etc.)Affected if You have Drop implementations that could panic while id-map is being modified
-
Check panic handling configurationExamine your Cargo.toml for panic = 'abort' settings or review if your code catches panics in contexts where remove_set and Drop interactAffected if Your project uses unwinding panics (not abort) and has code paths where Drop could panic during remove_set operations
You are affected if your project uses id-map crate version 2021-02-26 or earlier, calls remove_set, and has Drop implementations that can panic during the removal operation.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the id-map crate to a version after the 2021-02-26 vulnerability disclosure that includes a patch for this double-free issue, or review and refactor Drop implementations to prevent panic scenarios during remove_set operations.
Fix this in Id Map
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30457 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-30457 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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