Use-after-free via cloning consumed iterator elements
Published Aug 8, 2021 · Updated Aug 4, 2024
Use-after-free in the heapless crate before 0.6.1 allows remote attackers to access freed values by cloning a partially consumed Vec iterator. The heapless::vec::IntoIter::clone implementation copies the entire backing Vec, including already-consumed elements whose values have been dropped, creating access to freed objects. Reachability requires consuming code to expose cloning after partial iteration; the published impact is limited to availability.
Summary
What happened
Use-after-free in the heapless crate before 0.6.1 allows remote attackers to access freed values by cloning a partially consumed Vec iterator. The heapless::vec::IntoIter::clone implementation copies the entire backing Vec, including already-consumed elements whose values have been dropped, creating access to freed objects. Reachability requires consuming code to expose cloning after partial iteration; the published impact is limited to availability.
The record
- CVE
- CVE-2020-36464
- Published
- Aug 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- IntoIter::clone partially consumed iterator 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