Memory corruption via unconstrained Send and Sync implementations
Published Jan 22, 2021 · Updated Aug 4, 2024
Memory corruption in Rust hashconsing before 1.1.0 allows context-dependent attackers to crash concurrent programs via shared non-Sync values. HConsed unconditionally implements Send and Sync for every contained type, allowing thread-unsafe values such as Cell to cross thread boundaries and create data races. Reachability requires a consuming program to place such a value in HConsed and use it concurrently; the demonstrated result is a segmentation fault from safe Rust code.
Summary
What happened
Memory corruption in Rust hashconsing before 1.1.0 allows context-dependent attackers to crash concurrent programs via shared non-Sync values. HConsed unconditionally implements Send and Sync for every contained type, allowing thread-unsafe values such as Cell to cross thread boundaries and create data races. Reachability requires a consuming program to place such a value in HConsed and use it concurrently; the demonstrated result is a segmentation fault from safe Rust code.
The record
- CVE
- CVE-2020-36215
- Published
- Jan 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, 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.
Public exploit references
- Safe Rust data-race segmentation-fault demonstrationproof 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