Memory corruption via duplicated VecDeque elements
Published Apr 11, 2021 · Updated Aug 4, 2024
Memory corruption in Rust standard library 1.48.0 allows context-dependent attackers to trigger use-after-free through VecDeque operations. VecDeque::make_contiguous mishandles a wrapped buffer after reserve and push operations, duplicating an element so later pop_front calls remove it twice. Reachability depends on application code invoking this sequence on attacker-influenced data; the bounded consequences are use-after-free or double free.
Summary
What happened
Memory corruption in Rust standard library 1.48.0 allows context-dependent attackers to trigger use-after-free through VecDeque operations. VecDeque::make_contiguous mishandles a wrapped buffer after reserve and push operations, duplicating an element so later pop_front calls remove it twice. Reachability depends on application code invoking this sequence on attacker-influenced data; the bounded consequences are use-after-free or double free.
The record
- CVE
- CVE-2020-36318
- Published
- Apr 11, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 11, 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.
Public exploit references
- deq-bug VecDeque reproductionproof 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