{"id":"CVE-2020-36461","aliases":["EUVD-2021-1924","GHSA-wxjf-9f4g-3v44","RUSTSEC-2020-0141"],"status":"published","title":"Data races in noise_search","description":"An issue was discovered in the noise_search crate through 2020-12-10 for Rust. There are unconditional implementations of Send and Sync for MvccRwLock.","severity":{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-11","score":0.0124,"percentile":0.69546,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-362","CWE-77"],"published":"2020-12-10T12:00:00Z","modified":"2026-06-17T03:15:32Z","affected":[{"source":"ghsa","ecosystem":"crates.io","package":"noise_search","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.7.0"}]}]},{"source":"osv","ecosystem":"crates.io","package":"noise_search","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"0.7.0"}]}]},{"source":"osv","ecosystem":"crates.io","package":"noise_search","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"}]}]}],"products":[{"vendor":"noise_search_project","product":"noise_search"}],"references":[{"url":"https://rustsec.org/advisories/RUSTSEC-2020-0141.html","tags":["x_refsource_MISC","x_transferred","Exploit","Issue Tracking","Patch","Third Party Advisory","web","advisory"]},{"url":"https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/noise_search/RUSTSEC-2020-0141.md","tags":["x_refsource_MISC","x_transferred","Third Party Advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-36461","tags":["advisory"]},{"url":"https://github.com/pipedown/noise/issues/72","tags":["web","report"]},{"url":"https://github.com/advisories/GHSA-wxjf-9f4g-3v44"},{"url":"https://github.com/pipedown/noise","tags":["package"]},{"url":"https://crates.io/crates/noise_search","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2020-36461","description":"An issue was discovered in the noise_search crate through 2020-12-10 for Rust. There are unconditional implementations of Send and Sync for MvccRwLock.","status":"published","published":"2021-08-08T05:13:33Z","modified":"2024-08-04T17:30:08.044Z","updated_at":"2026-11-02T14:35:54.80237Z"}],"euvd":[{"id":"EUVD-2021-1924","description":"An issue was discovered in the noise_search crate through 2020-12-10 for Rust. There are unconditional implementations of Send and Sync for MvccRwLock.","status":"published","published":"2021-08-08T05:13:33Z","modified":"2024-08-04T17:30:08Z","updated_at":"2026-11-03T03:07:02.510914Z"}],"ghsa":[{"id":"GHSA-wxjf-9f4g-3v44","title":"Data races in noise_search","description":"Affected versions of the `noise_search` crate unconditionally implement Send/Sync for `MvccRwLock`.\nThis can lead to data races when types that are either `!Send` or `!Sync` (e.g. `Rc\u003cT\u003e`, `Arc\u003cCell\u003c_\u003e\u003e`) 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).\n\nAlso, safe APIs of `MvccRwLock` allow aliasing violations by allowing `\u0026T` and `LockResult\u003cMutexGuard\u003cBox\u003cT\u003e\u003e\u003e` 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).\n","status":"published","published":"2021-08-25T20:56:05Z","modified":"2023-02-01T05:05:52Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-77","CWE-362"],"updated_at":"2026-11-02T14:36:35.781528Z"}],"nvd":[{"id":"CVE-2020-36461","description":"An issue was discovered in the noise_search crate through 2020-12-10 for Rust. There are unconditional implementations of Send and Sync for MvccRwLock.","status":"published","published":"2021-08-08T06:15:07.963Z","modified":"2026-06-17T03:15:32.49Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":6.8,"vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","level":"medium","assessor":"primary"}],"cwes":["CWE-77"],"updated_at":"2026-11-02T14:06:44.292752Z"}],"osv":[{"id":"GHSA-wxjf-9f4g-3v44","title":"Data races in noise_search","description":"Affected versions of the `noise_search` crate unconditionally implement Send/Sync for `MvccRwLock`.\nThis can lead to data races when types that are either `!Send` or `!Sync` (e.g. `Rc\u003cT\u003e`, `Arc\u003cCell\u003c_\u003e\u003e`) 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).\n\nAlso, safe APIs of `MvccRwLock` allow aliasing violations by allowing `\u0026T` and `LockResult\u003cMutexGuard\u003cBox\u003cT\u003e\u003e\u003e` 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).\n","status":"published","published":"2021-08-25T20:56:05Z","modified":"2023-11-08T04:03:46.256345Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-362","CWE-77"],"updated_at":"2026-11-02T15:46:59.131095Z"},{"id":"RUSTSEC-2020-0141","title":"MvccRwLock allows data races \u0026 aliasing violations","description":"Affected versions of this crate unconditionally implement Send/Sync for `MvccRwLock`.\nThis can lead to data races when types that are either `!Send` or `!Sync` (e.g. `Rc\u003cT\u003e`, `Arc\u003cCell\u003c_\u003e\u003e`) 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).\n\nAlso, safe APIs of `MvccRwLock` allow aliasing violations by allowing `\u0026T` and `LockResult\u003cMutexGuard\u003cBox\u003cT\u003e\u003e\u003e` 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).","status":"published","published":"2020-12-10T12:00:00Z","modified":"2023-11-08T04:03:46.256345Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:39.492624Z"}]}}