2902 matches found
CVE-2020-36445
The CVE-2020-36445 issue affects the Rust crate convec, where ConVec provides unconditional Send/Sync implementations through 2020-11-24. Root cause: ConVec exposes Send and Sync for all T, enabling insertion of non-Send or non-Sync types (e.g., Arc<Cell> or Rc) and creating data races. Imp...
CVE-2020-36445
An issue was discovered in the convec crate through 2020-11-24 for Rust. There are unconditional implementations of Send and Sync for ConVec...
CVE-2020-36446
An issue was discovered in the signal-simple crate through 2020-11-15 for Rust. There are unconditional implementations of Send and Sync for SyncChannel...
CVE-2020-36446
CVE-2020-36446 affects the signal-simple crate for Rust. The root cause is that SyncChannel is implemented as Send and Sync unconditionally, which allows moving or sharing owned T across threads. This can enable unsafe behavior when T is not Send, potentially causing data races and memory corrupt...
CVE-2020-36448
The CVE-2020-36448 entry concerns the Rust cache crate, where unconditional implementations of Send/Sync for Cache allow non-Send or non-Sync K types to be used. The root cause is that Cache exposes Send/Sync without requiring K to implement these traits, enabling potential data races when non-Se...
CVE-2020-36448
An issue was discovered in the cache crate through 2020-11-24 for Rust. There are unconditional implementations of Send and Sync for Cache...
CVE-2020-36449
An issue was discovered in the kekbit crate before 0.3.4 for Rust. For ShmWriter, Send is implemented without requiring H: Send...
CVE-2020-36450
The CVE-2020-36450 issue affects the Rust crate payload “bunch” (through 2020-11-12) where Bunch unconditionally implements Send and Sync. This design allows inserting T values that are not Send/Sync (e.g., T: !Send, T: !Sync) and using Bunch across threads (for example via Bunch::get() returning...
CVE-2020-36450
An issue was discovered in the bunch crate through 2020-11-12 for Rust. There are unconditional implementations of Send and Sync for Bunch...
CVE-2020-36451
CVE-2020-36451 affects the Rust rcu_cell crate, where RcuCell unconditionally implements Send/Sync. This configuration allows sending T in a non-Send context and concurrent access to non-Sync T via RcuCell, creating a data-race risk and potential memory corruption. Public references from multiple...
CVE-2020-36451
An issue was discovered in the rcucell crate through 2020-11-14 for Rust. There are unconditional implementations of Send and Sync for RcuCell...
CVE-2020-36453
An issue was discovered in the scottqueue crate through 2020-11-15 for Rust. There are unconditional implementations of Send and Sync for Queue...
CVE-2020-36454
CVE-2020-36454 concerns the Rust crate parc . The issue is that the type LockWeak has an unconditional implementation of Send without trait bounds on T , and it does not own the underlying data (it only provides &T ). This enables concurrent access to a non-Sync type, which can lead to undefined ...
CVE-2020-36455
An issue was discovered in the slock crate through 2020-11-17 for Rust. Slock unconditionally implements Send and Sync...
CVE-2020-36455
An issue was discovered in the slock crate through 2020-11-17 for Rust. Slock unconditionally implements Send and Sync...
CVE-2020-36456
The CVE-2020-36456 entry concerns the Rust crate toolshed, specifically the CopyCell type. The root cause is that the Send trait for CopyCell lacks bounds on the contained type, enabling potential data races when sending CopyCell across threads. Documented impact includes data race conditions due...
CVE-2020-36456
An issue was discovered in the toolshed crate through 2020-11-15 for Rust. In CopyCell, the Send trait lacks bounds on the contained type...
CVE-2020-36457
An issue was discovered in the lever crate before 0.1.1 for Rust. AtomicBox implements the Send and Sync traits for all types T...
CVE-2020-36457
CVE-2020-36457 affects the lever crate for Rust, specifically versions before 0.1.1. The root cause is that an internal type, AtomicBox, implements Send and Sync for all types T, which enables non-Send types (e.g., Rc) and non-Sync types (e.g., Cell) to be used across thread boundaries. This can ...