https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-17T04:43:25.286683+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cve-2020-36441 CVE-2020-36441 2026-10-17T04:43:25.288213+00:00

An issue was discovered in the abox crate before 0.4.1 for Rust. It implements Send and Sync for AtomicBox<T> with no requirement for T: Send and T: Sync.

 https://cve.radiocsirt.org/vuln/rustsec-2020-0121 RUSTSEC-2020-0121 — AtomicBox<T> implements Send/Sync for any `T: Sized` 2026-10-17T04:43:25.288262+00:00

Affected: crates.io: abox

Affected versions of this crate implements `Send`/`Sync` for `AtomicBox<T>` without requiring `T: Send`/`T: Sync`. This allows to create data races to `T: !Sync` and send `T: !Send` to another thread.

Such behavior breaks the compile-time thread safety guarantees of Rust, and allows users to incur undefined behavior using safe Rust (e.g. memory corruption from data race).

The flaw was corrected in commit 34c2b9e by adding trait bound `T: Send` to `Send` impl for `AtomicBox<T>` and trait bound `T: Sync` to `Sync` impl for `AtomicBox<T>`.