CVE-2020-35927

An issue was discovered in the thex crate through 2020-12-08 for Rust. Thex allows cross-thread data races of non-Send types...

CVE-2020-35927

The CVE-2020-35927 entry concerns the Rust thex crate, where Thex allows cross-thread data races of non-Send types. The issue arises because Thex implements Sync for all T but lacks a Send bound for T, enabling non-Send types (e.g., Rc) to be transferred across threads, which can trigger undefine...

Rust 竞争条件问题漏洞

Rust is a general-purpose, compiled programming language from the Mozilla Foundation. A Competition Condition Issue vulnerability exists in Rust concread crate versions prior to 0.2.6, which can be exploited by an attacker to cause data contention in ARCache by sending a type that does not...

CVE-2020-35924: Out-of-bounds Write

An issue was discovered in the try-mutex crate before 0.3.0 for Rust. TryMutex allows cross-thread sending of a non-Send type...

CVE-2020-35927: Undefined Security Weakness

An issue was discovered in the thex crate through 2020-12-08 for Rust. Thex allows cross-thread data races of non-Send types...

CVE-2020-35925: Undefined Security Weakness

An issue was discovered in the magnetic crate before 2.0.1 for Rust. MPMCConsumer and MPMCProducer allow cross-thread sending of a non-Send type...

RUSTSEC-2020-0143 Queues allow non-Send types to be sent to other threads, allowing data races

Affected versions of this crate unconditionally implemented Send for types used in queue implementations InnerSend, InnerRecv, FutInnerSend, FutInnerRecv. This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior...

Queues allow non-Send types to be sent to other threads, allowing data races

Affected versions of this crate unconditionally implemented Send for types used in queue implementations InnerSend, InnerRecv, FutInnerSend, FutInnerRecv. This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior...

RUSTSEC-2020-0106 Queues allow non-Send types to be sent to other threads, allowing data races

Affected versions of this crate unconditionally implemented Send for types used in queue implementations InnerSend, InnerRecv, FutInnerSend, FutInnerRecv. This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior. The flaw was correcte...

Queues allow non-Send types to be sent to other threads, allowing data races

Affected versions of this crate unconditionally implemented Send for types used in queue implementations InnerSend, InnerRecv, FutInnerSend, FutInnerRecv. This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior. The flaw was correcte...

ButtplugFutureStateShared allows data race to (!Send|!Sync) objects

ButtplugFutureStateShared implements Send & Sync regardless of T. If T: !Send for ButtplugFutureStateShared, it is possible to move non-Send types across thread boundaries e.g. T=Rc and lead to undefined behavior. If T: !Sync for ButtplugFutureStateShared, it is possible to cause data race to T...

ShmWriter allows sending non-Send type across threads

Affected versions of this crate implement Send for ShmWriter without requiring H: Send. This allows users to send H: !Send to other threads, which can potentially lead to data races and undefined behavior...

RUSTSEC-2020-0129 ShmWriter allows sending non-Send type across threads

Affected versions of this crate implement Send for ShmWriter without requiring H: Send. This allows users to send H: !Send to other threads, which can potentially lead to data races and undefined behavior...

RUSTSEC-2020-0124 ArcGuard's Send and Sync should have bounds on RC

Affected versions of this crate implement Send/Sync for ArcGuard with no trait bounds on RC. This allows users to send RC: !Send to other threads and also allows users to concurrently access Rc: !Sync from multiple threads. This can result in memory corruption from data race or other undefined...

PT-2020-17559

Name of the Vulnerable Software and Affected Versions thex crate through 2020-12-08 Description An issue in the thex crate allows cross-thread data races of non-Send types. Specifically, thex::Thex implements Sync for all types T, but it is missing a bound for T: Send. This allows non-Send types,...

PT-2020-17644

Name of the Vulnerable Software and Affected Versions syncpool crate versions prior to 0.1.6 Description An issue in the syncpool crate allows sending non-Send types to other threads, leading to data races when non-Send types like Cell or Rc are contained inside Bucket2 and sent across thread...

PT-2020-17625

Name of the Vulnerable Software and Affected Versions convec crate through 2020-11-24 Description The issue allows users to insert types that are not Send or not Sync into ConVec, enabling the creation of data races. This can be achieved by using non-Send types like Arc or Rc as T in ConVec, or b...

PT-2020-17616

Name of the Vulnerable Software and Affected Versions conqueue crate versions prior to 0.4.0 Description The issue allows sending non-Send types to other threads by invoking &QueueSender.send, which can lead to memory corruption by creating data races with types like Rc or Arc. Recommendations Fo...

RUSTSEC-2020-0119 ReadTicket and WriteTicket should only be sendable when T is Send

Affected versions of this crate unconditionally implemented Send for ReadTicket & WriteTicket. This allows to send non-Send T to other threads. This can allows creating data races by cloning types with internal mutability and sending them to other threads as T of ReadTicket/WriteTicket. Such data...

TryMutex<T> allows sending non-Send type across threads

Affected versions of this crate unconditionally implemented Sync trait for TryMutex type. This allows users to put non-Send T type in TryMutex and send it to another thread, which can cause a data race. The flaw was corrected in the 0.3.0 release by adding T: Send bound for the Sync trait...