RUSTSEC-2020-0116

    Dashboard / Vulnerabilities / RUSTSEC-2020-0116

    RUSTSEC-2020-0116

    Published: 15 Nov 2020Last Modified: 8 Nov 2023

    Summary: PinSlab<T> and Unordered<T, S> need bounds on their Send/Sync traits

    Details: Affected versions of this crate unconditionally implemented `Send` & `Sync` for types `PinSlab<T>` & `Unordered<T, S>`. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads. This can result in a data race & memory corruption when types that provide internal mutability without synchronization are contained within `PinSlab<T>` or `Unordered<T, S>` and accessed concurrently from multiple threads. The flaw was corrected in commits 92f40b4 & 6a6c367 by adding trait bound `T: Send` to `Send` impls for `PinSlab<T>` & `Unordered<T, S>` and adding `T: Sync` to `Sync` impls for `PinSlab<T>` & `Unordered<T, S>`.

    References: https://crates.io/crates/unicycle, https://rustsec.org/advisories/RUSTSEC-2020-0116.html, https://github.com/udoprog/unicycle/issues/8

    Affected packages

    Package

    Name: unicycle

    Purl: pkg:cargo/unicycle

    Affected ranges

    Type: SEMVER

    Events:

    Introduced- 0.0.0-0
    Fixed -0.7.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-0116 | CVE-DB