OMGeeky/advisory-db
1
0
Fork 0
mirror of https://github.com/OMGeeky/advisory-db.git synced 2026-02-15 22:04:38 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
cb9432ef2adc2cdeae9dfbe9ae0ffe4a4ed8b7e2
advisory-db/crates/unicycle/RUSTSEC-2020-0116.md
Yechan Bae a19397dee4 Add thread-safety category to relevant bugs
2021-01-30 23:02:50 -05:00

976 B
Raw Blame History 

[advisory]
id = "RUSTSEC-2020-0116"
package = "unicycle"
date = "2020-11-15"
url = "https://github.com/udoprog/unicycle/issues/8"
categories = ["memory-corruption", "thread-safety"]

[versions]
patched = [">= 0.7.1"]

PinSlab and Unordered<T, S> need bounds on their Send/Sync traits

Affected versions of this crate unconditionally implemented Send & Sync for types PinSlab<T> & Unordered<T, S>. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.

This can result in a data race & memory corruption when types that provide internal mutability without synchronization are contained within PinSlab<T> or Unordered<T, S> and accessed concurrently from multiple threads.

The flaw was corrected in commits 92f40b4 & 6a6c367 by adding trait bound T: Send to Send impls for PinSlab<T> & Unordered<T, S> and adding T: Sync to Sync impls for PinSlab<T> & Unordered<T, S>.