Process memory corruption via panic-unsafe map cloning
Published Apr 7, 2021 · Updated Aug 3, 2024
Double free in the id-map crate 0.2.1 and earlier allows attackers to corrupt memory when cloning a map whose value clone panics. IdMap::clone_from drops existing values and replaces its ID set before cloning replacements, so a panic leaves old slots marked live and drops them again. The vulnerable path requires a stored value's Clone implementation to panic; the resulting double free can crash or corrupt the consuming process.
Summary
What happened
Double free in the id-map crate 0.2.1 and earlier allows attackers to corrupt memory when cloning a map whose value clone panics. IdMap::clone_from drops existing values and replaces its ID set before cloning replacements, so a panic leaves old slots marked live and drops them again. The vulnerable path requires a stored value's Clone implementation to panic; the resulting double free can crash or corrupt the consuming process.
The record
- CVE
- CVE-2021-30455
- Published
- Apr 7, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- IdMap clone_from panic reproducerproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo