Memory corruption via unconditional Send implementation
Published Aug 8, 2021 · Updated Aug 4, 2024
A data race in the syncpool crate before 0.1.6 allows attackers to trigger memory corruption by moving non-Send values across threads. The unsafe Send implementation for Bucket2 omits a T: Send bound, so SyncPool can transfer Cell or Rc values across thread boundaries. Exploitation requires an application to place a non-Send value in Bucket2 and move it between threads, producing undefined behavior that can crash the process or corrupt memory.
Summary
What happened
A data race in the syncpool crate before 0.1.6 allows attackers to trigger memory corruption by moving non-Send values across threads. The unsafe Send implementation for Bucket2 omits a T: Send bound, so SyncPool can transfer Cell or Rc values across thread boundaries. Exploitation requires an application to place a non-Send value in Bucket2 and move it between threads, producing undefined behavior that can crash the process or corrupt memory.
The record
- CVE
- CVE-2020-36462
- Published
- Aug 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-77, CWE-362
- 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.
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
- Bucket2 undefined-behavior 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