unicycle
Affected
- introduced
0.0.0-0, fixed0.10.3(semver)
Fixed versions
0.10.3
Fix
- Fixed version
0.10.3cargo update -p unicycle --precise 0.10.3
Advisory
Also known as: GHSA-8gw6-724c-9h38
Use-after-free when a future's Drop panics while the container is dropped
Storage::clear walks the slab, empties each entry and frees the Task
allocation once its reference count reaches zero. self.tasks.set_len(0) only
runs after the loop.
Emptying an entry drops the user future it holds, and T carries no bounds
excluding a panicking Drop. If one unwinds, the length is never committed andself.tasks still holds the pointers already processed. Drop for Storage
calls clear again, and the second pass dereferences (*task.as_ptr()).entry
on allocations the first pass already freed — a use-after-free (CWE-416)
reachable from safe Rust.
Storage is reached only through Unordered, whose Drop calls clear. No
particular method call is needed; dropping the container is enough.
Mitigation
Update to 0.10.3.
Not rated by the source.
0.0.0-0, fixed 0.10.3 (semver)0.10.3
0.10.3cargo update -p unicycle --precise 0.10.3Fix 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