RUSTSEC-2020-0121

    Dashboard / Vulnerabilities / RUSTSEC-2020-0121

    RUSTSEC-2020-0121

    Published: 10 Nov 2020Last Modified: 8 Nov 2023

    Summary: AtomicBox<T> implements Send/Sync for any `T: Sized`

    Details: 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>`.

    References: https://crates.io/crates/abox, https://rustsec.org/advisories/RUSTSEC-2020-0121.html, https://github.com/SonicFrog/abox/issues/1

    Affected packages

    Package

    Name: abox

    Purl: pkg:cargo/abox

    Affected ranges

    Type: SEMVER

    Events:

    Introduced- 0.0.0-0
    Fixed -0.4.1

    Affected versions

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High
    RUSTSEC-2020-0121 | CVE-DB