futures-util
Affected
- introduced
0.3.0, fixed0.3.2(semver)
Fixed versions
0.3.2
Fix
- Fixed version
0.3.2cargo update -p futures-util --precise 0.3.2
Advisory
Also known as: CVE-2020-35908, GHSA-5r9g-j7jj-hw6c
Improper Sync implementation on FuturesUnordered in futures-utils can cause data corruption
Affected versions of the crate had an unsound Sync implementation on the FuturesUnordered structure, which used a Cell for
interior mutability without any code to handle synchronized access to the underlying task list's length and head safely.
This could of lead to data corruption since two threads modifying the list at once could see incorrect values due to the lack
of access synchronization.
The issue was fixed by adding access synchronization code around insertion of tasks into the list.
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.3.0, fixed 0.3.2 (semver)0.3.2
0.3.2cargo update -p futures-util --precise 0.3.2Fix 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