futures-intrusive
Affected
- introduced
0, fixed0.4.0(semver)
Fixed versions
0.4.0
Fix
- Fixed version
0.4.0cargo update -p futures-intrusive --precise 0.4.0
Advisory
Also known as: CVE-2020-35915, RUSTSEC-2020-0072
Data races in futures-intrusive
GenericMutexGuard<T> was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is.
This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code.
The flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait.
Medium Basis: The source's own band: MODERATE
0, fixed 0.4.0 (semver)0.4.0
0.4.0cargo update -p futures-intrusive --precise 0.4.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0