CVE-2020-35928

An issue was discovered in the concread crate before 0.2.6 for Rust. Attackers can cause an ARCache data race by sending types that do not implement Send/Sync...

Cross site scripting

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...

Cross site scripting

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

Sql injection

An issue was discovered in the concread crate before 0.2.6 for Rust. Attackers can cause an ARCache data race by sending types that do not implement Send/Sync...

Cross site scripting

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...

CVE-2020-35924

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-35924

CVE-2020-35924 affects the Rust crate try-mutex prior to 0.3.0. The issue arises because TryMutex allowed cross-thread sending of non-Send types due to an unconditional Sync implementation, enabling data races. The root cause is absence of a Send bound on the Sync trait implementation for TryMute...

CVE-2020-35925

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...

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...

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-35928

Concread crate (Rust) before 0.2.6 exposes a data race in ARCache when non-Send/Sync types are used. Root cause: ARCache implementation unbound by Send/Sync, allowing unsafe concurrent access. The issue was fixed in 0.2.6 by adding K: Send + Sync and V: Send + Sync bounds to the affected Send/Syn...

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...

Rust atom crate 竞争条件问题漏洞

Rust is a general-purpose, compiled programming language from the Mozilla Foundation. A security vulnerability exists in Rust atom crate, which stems from an insecure Send implementation that allows data contention across threads. No details of the vulnerability are provided at this time...

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-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...

The vulnerability of the xgmac_enet_send function in the hw/net/xgmac.c file of the QEMU hardware emulation software arises from a lack of mechanism for checking the size of copied data. This allows a malicious actor to gain access to protected information, compromise its integrity, and cause service failures.

The vulnerability of the xgmacenetsend function in the hw/net/xgmac.c file of the QEMU hardware emulation software is related to the lack of a mechanism for checking the size of copied data. Exploiting this vulnerability can allow an attacker to access protected information, compromise its...

RUSTSEC-2020-0101 conquer-once's OnceCell lacks Send bound for its Sync trait.

Affected versions of conquer-once implements Sync for its OnceCell type without restricting it to Sendable types. This allows non-Send but Sync types such as MutexGuard to be sent across threads leading to undefined behavior and memory corruption in concurrent programs. The issue was fixed by...

RUSTSEC-2020-0114 `Demuxer` can carry non-Send types across thread boundaries

In the affected versions of this crate, Demuxer unconditionally implemented Send with no trait bounds on T. This allows sending a non-Send type T across thread boundaries, which can cause undefined behavior like unlocking a mutex from a thread that didn't lock the mutex, or memory corruption from...

conquer-once's OnceCell lacks Send bound for its Sync trait.

Affected versions of conquer-once implements Sync for its OnceCell type without restricting it to Sendable types. This allows non-Send but Sync types such as MutexGuard to be sent across threads leading to undefined behavior and memory corruption in concurrent programs. The issue was fixed by...

RUSTSEC-2020-0108 Soundness issue: Input<R> can be misused to create data race to an object

Input implements Send without requiring R: Send. Affected versions of this crate allows users to send non-Send types to other threads, which can lead to undefined behavior such as data race and memory corruption. The flaw was corrected in version 0.5.1 by adding R: Send bound to the Send impl of...