3845 matches found
CVE-2020-36434
An issue was discovered in the sys-info crate before 0.8.0 for Rust. sysinfo::diskinfo calls can trigger a double free...
CVE-2020-36435
CVE-2020-36435 affects the Rust crate ruspiro-singleton prior to 0.4.1. The issue is that Singleton did not enforce bounds on Send and Sync, allowing non-Sync types (e.g., Cell) to be used in singletons and potentially cause data races. The vulnerability is captured across multiple catalogs (NVD,...
CVE-2020-36436
An issue was discovered in the unicycle crate before 0.7.1 for Rust. PinSlab and Unordered do not have bounds on their Send and Sync traits...
CVE-2020-36437
An issue was discovered in the conqueue crate before 0.4.0 for Rust. There are unconditional implementations of Send and Sync for QueueSender...
CVE-2020-36437
The CVE-2020-36437 issue concerns the Rust conqueue crate prior to 0.4.0. The root cause is unconditional implementations of Send and Sync for QueueSender, which permits sending non-Send values across threads via (&QueueSender).send(), enabling data races and potentially memory corruption. Affect...
CVE-2020-36438
An issue was discovered in the tinyfuture crate before 0.4.0 for Rust. Future does not have bounds on its Send and Sync traits...
CVE-2020-36439
An issue was discovered in the ticketedlock crate before 0.3.0 for Rust. There are unconditional implementations of Send for ReadTicket and WriteTicket...
CVE-2020-36440
CVE-2020-36440 : In the libsbc crate for Rust (before 0.1.5), the Decoder type implements Send for any R: Read, allowing it to carry an R that may not be Send. This can enable undefined behavior such as memory corruption or data races if the contained reader is moved across threads. The root caus...
CVE-2020-36440
An issue was discovered in the libsbc crate before 0.1.5 for Rust. For Decoder, it implements Send for any R: Read...
CVE-2020-36441
An issue was discovered in the abox crate before 0.4.1 for Rust. It implements Send and Sync for AtomicBox with no requirement for T: Send and T: Sync...
CVE-2020-36441
CVE-2020-36441 affects the Rust crate abox (pre-0.4.1). AtomicBox is marked Send/Sync without requiring T: Send and T: Sync, which can undermine thread-safety guarantees and enable data races if T is not Send/Sync. Public disclosures and security records (e.g., RUSTSEC-2020-0121, GHSA data race e...
CVE-2020-36442
An issue was discovered in the beef crate before 0.5.0 for Rust. beef::Cow has no Sync bound on its Send trait...
CVE-2020-36442
The CVE-2020-36442 issue concerns the beef crate for Rust (pre-0.5.0) where beef::Cow lacked a Sync bound on its Send trait. This omission enables data races by allowing Cow to hold non-Sync types (e.g., Cell/RefCell) inside, potentially leading to memory corruption. Several connected sources cor...
CVE-2020-36444
An issue was discovered in the async-coap crate through 2020-12-08 for Rust. Send and Sync are implemented for ArcGuard without trait bounds on RC...
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-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-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-36447
The CVE-2020-36447 entry concerns the Rust v9 crate (through 2020-12-18) where SyncRef unconditionally implements Sync. This authoritative detail is repeatedly reflected across multiple connected records (NVD, Red Hat, GHSA, OSV, CNVD, etc.). The underlying issue is that SyncRef derives Clone and...