Memory corruption via panic-triggered double free
Published Apr 7, 2021 · Updated Aug 3, 2024
Double free in id-map through 2021-02-26 allows attackers to corrupt process memory by triggering a panic in a supplied closure. The get_or_insert method reserves a slot before calling f, so a panic causes the map to drop uninitialized or previously freed memory. Reachability requires consuming code to call get_or_insert with a fallible user-supplied closure; a resulting panic can crash the process or corrupt its memory.
Summary
What happened
Double free in id-map through 2021-02-26 allows attackers to corrupt process memory by triggering a panic in a supplied closure. The get_or_insert method reserves a slot before calling f, so a panic causes the map to drop uninitialized or previously freed memory. Reachability requires consuming code to call get_or_insert with a fallible user-supplied closure; a resulting panic can crash the process or corrupt its memory.
The record
- CVE
- CVE-2021-30456
- Published
- Apr 7, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415
- Attack vector
- Unavailable
- Privileges
- Unavailable
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
No public exploit references are available in this record.
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