Memory corruption via panic-unsafe BinaryHeap sifting
Published Apr 11, 2021 · Updated Aug 6, 2024
Memory corruption in Rust before 1.2.0 allows attackers to trigger invalid destruction when a BinaryHeap element comparison panics. During sift_up or sift_down_range, the implementation replaces a moved element with zeroed memory but does not restore a valid value while unwinding, so later destruction treats the zeroed bytes as an arbitrary type. Reachability requires application code to process attacker-influenced values whose ordering comparison panics; the resulting undefined behavior can corrupt memory or crash the process.
Summary
What happened
Memory corruption in Rust before 1.2.0 allows attackers to trigger invalid destruction when a BinaryHeap element comparison panics. During sift_up or sift_down_range, the implementation replaces a moved element with zeroed memory but does not restore a valid value while unwinding, so later destruction treats the zeroed bytes as an arbitrary type. Reachability requires application code to process attacker-influenced values whose ordering comparison panics; the resulting undefined behavior can corrupt memory or crash the process.
The record
- CVE
- CVE-2015-20001
- Published
- Apr 11, 2021
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 6, 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