{"id":"CVE-2020-35915","aliases":["EUVD-2021-1560","GHSA-4hjg-cx88-g9f9","RUSTSEC-2020-0072"],"status":"published","title":"Data races in futures-intrusive","description":"An issue was discovered in the futures-intrusive crate before 0.4.0 for Rust. GenericMutexGuard allows cross-thread data races of non-Sync types.","severity":{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-10","score":0.00379,"percentile":0.32185,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-362"],"published":"2020-10-31T12:00:00Z","modified":"2026-06-17T03:14:35Z","fixes":[{"ecosystem":"crates.io","package":"futures-intrusive","fixed_in":["0.4.0"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"crates.io","package":"futures-intrusive","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.0"}]}]},{"source":"osv","ecosystem":"crates.io","package":"futures-intrusive","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.4.0"}]}]},{"source":"osv","ecosystem":"crates.io","package":"futures-intrusive","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"0.4.0"}]}]}],"products":[{"vendor":"futures-intrusive_project","product":"futures-intrusive"}],"references":[{"url":"https://rustsec.org/advisories/RUSTSEC-2020-0072.html","tags":["x_refsource_MISC","x_transferred","Exploit","Third Party Advisory","web","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-35915","tags":["advisory"]},{"url":"https://github.com/Matthias247/futures-intrusive/issues/53","tags":["web","report"]},{"url":"https://github.com/advisories/GHSA-4hjg-cx88-g9f9"},{"url":"https://github.com/Matthias247/futures-intrusive","tags":["package"]},{"url":"https://crates.io/crates/futures-intrusive","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2020-35915","description":"An issue was discovered in the futures-intrusive crate before 0.4.0 for Rust. GenericMutexGuard allows cross-thread data races of non-Sync types.","status":"published","published":"2020-12-31T08:18:59Z","modified":"2024-08-04T17:16:13.215Z","updated_at":"2026-11-02T14:35:58.331892Z"}],"euvd":[{"id":"EUVD-2021-1560","description":"An issue was discovered in the futures-intrusive crate before 0.4.0 for Rust. GenericMutexGuard allows cross-thread data races of non-Sync types.","status":"published","published":"2020-12-31T08:18:59Z","modified":"2024-08-04T17:16:13Z","updated_at":"2026-11-03T03:07:04.595509Z"}],"ghsa":[{"id":"GHSA-4hjg-cx88-g9f9","title":"Data races in futures-intrusive","description":"GenericMutexGuard\u003cT\u003e was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is.\n\nThis is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code.\n\nThe flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait.","status":"published","published":"2021-08-25T20:49:58Z","modified":"2023-06-13T18:10:46Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-362"],"updated_at":"2026-11-02T14:36:53.654352Z"}],"nvd":[{"id":"CVE-2020-35915","description":"An issue was discovered in the futures-intrusive crate before 0.4.0 for Rust. GenericMutexGuard allows cross-thread data races of non-Sync types.","status":"published","published":"2020-12-31T09:15:15.707Z","modified":"2026-06-17T03:14:35.86Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"},{"version":"2.0","score":2.1,"vector":"AV:L/AC:L/Au:N/C:N/I:N/A:P","level":"low","assessor":"primary"}],"updated_at":"2026-11-02T14:06:28.340168Z"}],"osv":[{"id":"GHSA-4hjg-cx88-g9f9","title":"Data races in futures-intrusive","description":"GenericMutexGuard\u003cT\u003e was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is.\n\nThis is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code.\n\nThe flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait.","status":"published","published":"2021-08-25T20:49:58Z","modified":"2023-11-08T04:03:39.161436Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-362"],"updated_at":"2026-11-02T15:46:37.148947Z"},{"id":"RUSTSEC-2020-0072","title":"GenericMutexGuard allows data races of non-Sync types across threads","description":"`GenericMutexGuard\u003cT\u003e` was given the `Sync` auto trait as long as `T` is `Send`\ndue to its contained members. However, since the guard is supposed to represent\nan **acquired lock** and allows concurrent access to the underlying data from\ndifferent threads, it should only be `Sync` when the underlying data is.\n\nThis is a soundness issue and allows data races, potentially leading to crashes\nand segfaults from safe Rust code.\n\nThe flaw was corrected by adding a `T: Send + Sync` bound for\n`GenericMutexGuard`'s `Sync` trait.\n\nThis bug is [similar to one](https://github.com/rust-lang/rust/issues/41622) in\n`std::sync::Mutex`.","status":"published","published":"2020-10-31T12:00:00Z","modified":"2023-11-08T04:03:39.161436Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:53:39.492624Z"}]}}