Application crash via panic-unsafe Vec iterator cleanup
Published Apr 14, 2021 · Updated Aug 3, 2024
Double free in the Rust standard library before 1.52.0 allows attackers to crash applications through a panicking element destructor. Vec::from_iter's in-place specialization drops remaining elements before advancing its source pointer, so unwinding after a Drop panic processes an already freed element again. Reachability requires an application to collect from a Vec iterator through that specialization while a remaining element's destructor panics; the published proof of concept ends in allocator-detected double free and process termination.
Summary
What happened
Double free in the Rust standard library before 1.52.0 allows attackers to crash applications through a panicking element destructor. Vec::from_iter's in-place specialization drops remaining elements before advancing its source pointer, so unwinding after a Drop panic processes an already freed element again. Reachability requires an application to collect from a Vec iterator through that specialization while a remaining element's destructor panics; the published proof of concept ends in allocator-detected double free and process termination.
The record
- CVE
- CVE-2021-31162
- Published
- Apr 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 14, 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
- Vec::from_iter panic-on-drop proof of conceptproof of concept · demonstrated
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