3822 matches found
CVE-2020-36462
An issue was discovered in the syncpool crate before 0.1.6 for Rust. There is an unconditional implementation of Send for Bucket2...
CVE-2020-36462
An issue was discovered in the syncpool crate before 0.1.6 for Rust. There is an unconditional implementation of Send for Bucket2...
CVE-2020-36463
An issue was discovered in the multiqueue crate through 2020-12-25 for Rust. There are unconditional implementations of Send for InnerSend, InnerRecv, FutInnerSend, and FutInnerRecv...
CVE-2020-36463
An issue was discovered in the multiqueue crate through 2020-12-25 for Rust. There are unconditional implementations of Send for InnerSend, InnerRecv, FutInnerSend, and FutInnerRecv...
CVE-2020-36466
An issue was discovered in the cgc crate through 2020-12-10 for Rust. Ptr implements Send and Sync for all types...
CVE-2020-36466
CVE-2020-36466 affects the Rust crate cgc (Ptr type) with multiple soundness issues. The Ptr type implements Send and Sync for all types, enabling potential data races by sending non-thread-safe data across threads. In addition, Ptr::get violates mutable aliasing rules by returning multiple mutab...
CVE-2020-36466
An issue was discovered in the cgc crate through 2020-12-10 for Rust. Ptr implements Send and Sync for all types...
CVE-2020-36469
The CVE-2020-36469 entry describes a data-race risk in the Rust appendix crate (Index) where Send and Sync are implemented unconditionally for generic K and V. This can permit multi-threaded usage with non-Send/Sync types, potentially causing data contention or races when these types populate the...
CVE-2020-36469
An issue was discovered in the appendix crate through 2020-11-15 for Rust. For the generic K and V type parameters, Send and Sync are implemented unconditionally...
CVE-2020-36471
An issue was discovered in the generator crate before 0.7.0 for Rust. It does not ensure that a function for yielding values has Send bounds...
CVE-2020-36471
An issue was discovered in the generator crate before 0.7.0 for Rust. It does not ensure that a function for yielding values has Send bounds...
CVE-2020-36471
CVE-2020-36471 concerns the Rust generator crate prior to 0.7.0, where the yielding function does not enforce Send bounds on the value yielded, while the Generator type is Send. This mismatch allows potential data races when generators are used across threads with non-Send components (e.g., Rc) i...
Rust 命令注入漏洞
Rust is a general-purpose, compiled programming language from the Mozilla Foundation. Rust suffers from a command injection vulnerability that stems from the cache crate in Rust having an unconditional send and synchronization implementation for cache...
Rust 缓冲区错误漏洞
Rust is a general-purpose, compiled programming language from the Mozilla Foundation. buffer overflow vulnerabilities exist in versions of Mozilla Rust prior to 0.3.0, stemming from the ticketedlock crate in Rust. there are unconditional Send implementations for ReadTicket and WriteTicket, which...
CVE-2020-36449: Improper Neutralization of Special Elements used in a Command
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-36457: Improper Neutralization of Special Elements used in a Command
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-36450: Improper Neutralization of Special Elements used in a Command
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-36469: Undefined Security Weakness
An issue was discovered in the appendix crate through 2020-11-15 for Rust. For the generic K and V type parameters, Send and Sync are implemented unconditionally...
CVE-2020-36435: Concurrent Execution using Shared Resource with Improper Synchronization
An issue was discovered in the ruspiro-singleton crate before 0.4.1 for Rust. In Singleton, Send and Sync do not have bounds checks...
CVE-2020-36438: Concurrent Execution using Shared Resource with Improper Synchronization
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...