Most recent entries from all

cnvd-2021-71652

EUVD-2026-48070

fkie_cve-2020-36208

An issue was discovered in the conquer-once crate before 0.3.2 for Rust. Thread crossing can occur for a non-Send but Sync type, leading to memory corruption.

GHSA-3jc5-5hc5-33gj — Data races in conquer-once

Affected: crates.io: conquer-once

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 adding a Send constraint to OnceCell.

gsd-2020-36208

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

Affected: crates.io: conquer-once

Affected versions of `conquer-once` implements `Sync` for its `OnceCell` type without restricting it to `Send`able 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 adding a `Send` constraint to `OnceCell`.