RUSTSEC-2020-0115

    Dashboard / Vulnerabilities / RUSTSEC-2020-0115

    RUSTSEC-2020-0115

    Published: 16 Nov 2020Last Modified: 8 Nov 2023

    Summary: Singleton lacks bounds on Send and Sync.

    Details: `Singleton<T>` is meant to be a static object that can be initialized lazily. In order to satisfy the requirement that `static` items must implement `Sync`, `Singleton` implemented both `Sync` and `Send` unconditionally. This allows for a bug where non-`Sync` types such as `Cell` can be used in singletons and cause data races in concurrent programs. The flaw was corrected in commit `b0d2bd20e` by adding trait bounds, requiring the contaiend type to implement `Sync`.

    References: https://crates.io/crates/ruspiro-singleton, https://rustsec.org/advisories/RUSTSEC-2020-0115.html, https://github.com/RusPiRo/ruspiro-singleton/issues/10

    Affected packages

    Package

    Name: ruspiro-singleton

    Purl: pkg:cargo/ruspiro-singleton

    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-0115 | CVE-DB