futures-intrusive
Affected
- introduced
0.0.0-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, GHSA-4hjg-cx88-g9f9
GenericMutexGuard allows data races of non-Sync types across threads
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 forGenericMutexGuard's Sync trait.
This bug is similar to one instd::sync::Mutex.
Medium Basis: CVSS v3 score 5.5, vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
0.0.0-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: RustSec Advisory Database · CC0-1.0