RUSTSEC-2020-0141

    Dashboard / Vulnerabilities / RUSTSEC-2020-0141

    RUSTSEC-2020-0141

    Published: 10 Dec 2020Last Modified: 8 Nov 2023

    Summary: MvccRwLock allows data races & aliasing violations

    Details: Affected versions of this crate unconditionally implement Send/Sync for `MvccRwLock`. This can lead to data races when types that are either `!Send` or `!Sync` (e.g. `Rc<T>`, `Arc<Cell<_>>`) are contained inside `MvccRwLock` and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue). Also, safe APIs of `MvccRwLock` allow aliasing violations by allowing `&T` and `LockResult<MutexGuard<Box<T>>>` to co-exist in conflicting lifetime regions. The APIs of `MvccRwLock` should either be marked as `unsafe` or `MbccRwLock` should be changed to private or pub(crate).

    References: https://crates.io/crates/noise_search, https://rustsec.org/advisories/RUSTSEC-2020-0141.html, https://github.com/pipedown/noise/issues/72

    Affected packages

    Package

    Name: noise_search

    Purl: pkg:cargo/noise_search

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