Undefined behavior via unconstrained Shared thread-safety traits
Published Aug 8, 2021 · Updated Aug 4, 2024
A data race in the Rust model crate 0.1.2 and earlier allows attackers to trigger undefined behavior through concurrent Shared use. Shared unconditionally implements the unsafe Send and Sync traits, even when T is not thread-safe, so safe code can share mutable state across threads without synchronization. Exploitation requires consuming code to place a non-Send or non-Sync inner value in Shared and access it concurrently; the published demonstration corrupts a pointer and crashes the process.
Summary
What happened
A data race in the Rust model crate 0.1.2 and earlier allows attackers to trigger undefined behavior through concurrent Shared use. Shared unconditionally implements the unsafe Send and Sync traits, even when T is not thread-safe, so safe code can share mutable state across threads without synchronization. Exploitation requires consuming code to place a non-Send or non-Sync inner value in Shared and access it concurrently; the published demonstration corrupts a pointer and crashes the process.
The record
- CVE
- CVE-2020-36460
- Published
- Aug 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, CWE-843
- 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
- Safe Rust Shared data-race 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