CVE-2020-36461 – noise_search

Package

Manager: cargo
Name: noise_search
Vulnerable Version: >=0 <=0.7.0

Severity

Level: Medium

CVSS v3.1: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS v4.0: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

EPSS: 0.00477 pctl0.64007

Details

Data races in noise_search Affected versions of the `noise_search` 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).

Metadata

Created: 2021-08-25T20:56:05Z
Modified: 2021-08-24T18:02:25Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/08/GHSA-wxjf-9f4g-3v44/GHSA-wxjf-9f4g-3v44.json
CWE IDs: ["CWE-362", "CWE-77"]
Alternative ID: GHSA-wxjf-9f4g-3v44
Finding: F124
Auto approve: 1