{"id":"CVE-2020-36444","aliases":["EUVD-2021-1661","GHSA-9j8q-m9x5-9g6j","RUSTSEC-2020-0124"],"status":"published","title":"Data races in async-coap","description":"An issue was discovered in the async-coap crate through 2020-12-08 for Rust. Send and Sync are implemented for ArcGuard\u003cRC, T\u003e without trait bounds on RC.","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.00766,"percentile":0.55903,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-119","CWE-362"],"published":"2020-12-08T12:00:00Z","modified":"2026-06-17T03:15:30Z","affected":[{"source":"ghsa","ecosystem":"crates.io","package":"async-coap","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.1.0"}]}]},{"source":"osv","ecosystem":"crates.io","package":"async-coap","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"0.1.0"}]}]},{"source":"osv","ecosystem":"crates.io","package":"async-coap","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"}]}]}],"products":[{"vendor":"async-coap_project","product":"async-coap"}],"references":[{"url":"https://rustsec.org/advisories/RUSTSEC-2020-0124.html","tags":["x_refsource_MISC","x_transferred","Third Party Advisory","web","advisory"]},{"url":"https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/async-coap/RUSTSEC-2020-0124.md","tags":["x_refsource_MISC","x_transferred","Third Party Advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-36444","tags":["advisory"]},{"url":"https://github.com/google/rust-async-coap/issues/33","tags":["web","report"]},{"url":"https://github.com/advisories/GHSA-9j8q-m9x5-9g6j"},{"url":"https://github.com/google/rust-async-coap","tags":["package"]},{"url":"https://crates.io/crates/async-coap","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2020-36444","description":"An issue was discovered in the async-coap crate through 2020-12-08 for Rust. Send and Sync are implemented for ArcGuard\u003cRC, T\u003e without trait bounds on RC.","status":"published","published":"2021-08-08T05:17:13Z","modified":"2024-08-04T17:30:07.55Z","updated_at":"2026-11-02T14:35:54.80237Z"}],"euvd":[{"id":"EUVD-2021-1661","description":"An issue was discovered in the async-coap crate through 2020-12-08 for Rust. Send and Sync are implemented for ArcGuard\u003cRC, T\u003e without trait bounds on RC.","status":"published","published":"2021-08-08T05:17:13Z","modified":"2024-08-04T17:30:07Z","updated_at":"2026-11-03T03:07:03.010139Z"}],"ghsa":[{"id":"GHSA-9j8q-m9x5-9g6j","title":"Data races in async-coap","description":"An issue was discovered in the async-coap crate through 2020-12-08 for Rust. \nAffected versions of this crate implement Send/Sync for `ArcGuard\u003cRC, T\u003e` with no trait bounds on `RC`. This allows users to send `RC: !Send` to other threads and also allows users to concurrently access `Rc: !Sync` from multiple threads.\n\nThis can result in memory corruption from data race or other undefined behavior caused by sending `T: !Send` to other threads (e.g. dropping `MutexGuard\u003cT\u003e` in another thread that didn't lock its mutex).\n","status":"published","published":"2021-08-25T20:59:11Z","modified":"2023-01-27T05:00:55Z","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-119","CWE-362"],"updated_at":"2026-11-02T14:36:15.574072Z"}],"nvd":[{"id":"CVE-2020-36444","description":"An issue was discovered in the async-coap crate through 2020-12-08 for Rust. Send and Sync are implemented for ArcGuard\u003cRC, T\u003e without trait bounds on RC.","status":"published","published":"2021-08-08T06:15:07.277Z","modified":"2026-06-17T03:15:30.32Z","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-362"],"updated_at":"2026-11-02T14:06:44.292752Z"}],"osv":[{"id":"GHSA-9j8q-m9x5-9g6j","title":"Data races in async-coap","description":"An issue was discovered in the async-coap crate through 2020-12-08 for Rust. \nAffected versions of this crate implement Send/Sync for `ArcGuard\u003cRC, T\u003e` with no trait bounds on `RC`. This allows users to send `RC: !Send` to other threads and also allows users to concurrently access `Rc: !Sync` from multiple threads.\n\nThis can result in memory corruption from data race or other undefined behavior caused by sending `T: !Send` to other threads (e.g. dropping `MutexGuard\u003cT\u003e` in another thread that didn't lock its mutex).\n","status":"published","published":"2021-08-25T20:59:11Z","modified":"2023-11-08T04:03:45.205946Z","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-119","CWE-362"],"updated_at":"2026-11-02T15:46:43.875515Z"},{"id":"RUSTSEC-2020-0124","title":"ArcGuard's Send and Sync should have bounds on RC","description":"Affected versions of this crate implement Send/Sync for `ArcGuard\u003cRC, T\u003e` with no trait bounds on `RC`. This allows users to send `RC: !Send` to other threads and also allows users to concurrently access `Rc: !Sync` from multiple threads.\n\nThis can result in memory corruption from data race or other undefined behavior caused by sending `T: !Send` to other threads (e.g. dropping `MutexGuard\u003cT\u003e` in another thread that didn't lock its mutex).","status":"published","published":"2020-12-08T12:00:00Z","modified":"2023-11-08T04:03:45.205946Z","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"}]}}