RUSTSEC-2020-0126

    Dashboard / Vulnerabilities / RUSTSEC-2020-0126

    RUSTSEC-2020-0126

    Published: 15 Nov 2020Last Modified: 8 Nov 2023

    Summary: SyncChannel<T> can move 'T: !Send' to other threads

    Details: Affected versions of this crate unconditionally implement Send/Sync for `SyncChannel<T>`. `SyncChannel<T>` doesn't provide access to `&T` but merely serves as a channel that consumes and returns owned `T`. Users can create UB in safe Rust by sending `T: !Send` to other threads with `SyncChannel::send/recv` APIs. Using `T = Arc<Cell<_>` allows to create data races (which can lead to memory corruption), and using `T = MutexGuard<T>` allows to unlock a mutex from a thread that didn't lock the mutex.

    References: https://crates.io/crates/signal-simple, https://rustsec.org/advisories/RUSTSEC-2020-0126.html, https://github.com/kitsuneninetails/signal-rust/issues/2

    Affected packages

    Package

    Name: signal-simple

    Purl: pkg:cargo/signal-simple

    Affected ranges

    Type: SEMVER

    Events:

    Introduced- 0.0.0-0
    Fixed -None

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