Memory corruption via unconditional Send implementations
Published Jan 22, 2021 · Updated Aug 4, 2024
Data race in the multiqueue2 crate before 0.1.7 allows attackers to corrupt memory or crash a process by moving non-Send values across threads. Four unsafe Send implementations omit a T: Send bound, causing safe Rust to treat InnerSend, InnerRecv, FutInnerSend, and FutInnerRecv values as transferable across threads regardless of their contained type. Exploitation requires a consuming application to place an attacker-influenced non-Send value into an affected queue; demonstrated outcomes include memory corruption, a memory leak, and a process crash.
Summary
What happened
Data race in the multiqueue2 crate before 0.1.7 allows attackers to corrupt memory or crash a process by moving non-Send values across threads. Four unsafe Send implementations omit a T: Send bound, causing safe Rust to treat InnerSend, InnerRecv, FutInnerSend, and FutInnerRecv values as transferable across threads regardless of their contained type. Exploitation requires a consuming application to place an attacker-influenced non-Send value into an affected queue; demonstrated outcomes include memory corruption, a memory leak, and a process crash.
The record
- CVE
- CVE-2020-36214
- Published
- Jan 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-662
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 22, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Upstream issue proof-of-concept programsproof 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