Memory-safety violation via unsound MutexGuard Sync bound
Published Apr 14, 2021 · Updated Aug 5, 2024
Race condition in the Rust standard library before 1.19.0 allows attackers to violate memory safety through concurrent MutexGuard access. MutexGuard incorrectly implements Sync when T is merely Send, exposing non-Sync interior-mutability types through shared guard references. Exploitation requires an affected program to share such a guard across threads, where unsynchronized reads and writes can corrupt protected data.
Summary
What happened
Race condition in the Rust standard library before 1.19.0 allows attackers to violate memory safety through concurrent MutexGuard access. MutexGuard incorrectly implements Sync when T is merely Send, exposing non-Sync interior-mutability types through shared guard references. Exploitation requires an affected program to share such a guard across threads, where unsynchronized reads and writes can corrupt protected data.
The record
- CVE
- CVE-2017-20004
- Published
- Apr 14, 2021
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 14, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 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
- MutexGuard<Cell<i32>> data-race reproducerproof 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