Memory corruption via unsound Send and Sync bounds
Published Aug 8, 2021 · Updated Aug 4, 2024
Data races in the tiny_future crate before 0.4.0 allow attackers to corrupt memory when concurrent programs use non-thread-safe values. Future declares Send and Sync without requiring T to implement those traits, allowing values such as Cell to cross thread-safety boundaries. Exploitation requires a consuming application to store a non-thread-safe value in Future and access it concurrently; that application determines what memory is exposed to the race.
Summary
What happened
Data races in the tiny_future crate before 0.4.0 allow attackers to corrupt memory when concurrent programs use non-thread-safe values. Future declares Send and Sync without requiring T to implement those traits, allowing values such as Cell to cross thread-safety boundaries. Exploitation requires a consuming application to store a non-thread-safe value in Future and access it concurrently; that application determines what memory is exposed to the race.
The record
- CVE
- CVE-2020-36438
- Published
- Aug 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- 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.
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