{"id":"CVE-2020-36206","aliases":["EUVD-2021-1663","GHSA-9mxw-4856-9cm5","RUSTSEC-2020-0098"],"status":"published","title":"Data races in rusb","description":"An issue was discovered in the rusb crate before 0.7.0 for Rust. Because of a lack of Send and Sync bounds, a data race and memory corruption can occur.","severity":{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-11","score":0.00289,"percentile":0.21685,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-662","CWE-787"],"published":"2020-12-18T12:00:00Z","modified":"2026-10-24T10:30:19Z","fixes":[{"ecosystem":"crates.io","package":"rusb","fixed_in":["0.7.0"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"crates.io","package":"rusb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.7.0"}]}]},{"source":"osv","ecosystem":"crates.io","package":"rusb","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.7.0"}]}]},{"source":"osv","ecosystem":"crates.io","package":"rusb","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"0.7.0"}]}]}],"products":[{"vendor":"rusb_project","product":"rusb"}],"references":[{"url":"https://rustsec.org/advisories/RUSTSEC-2020-0098.html","tags":["x_refsource_MISC","x_transferred","Vendor Advisory","advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-36206","tags":["advisory"]},{"url":"https://github.com/a1ien/rusb/issues/44","tags":["web","report"]},{"url":"https://github.com/advisories/GHSA-9mxw-4856-9cm5"},{"url":"https://github.com/a1ien/rusb","tags":["package"]},{"url":"https://crates.io/crates/rusb","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2020-36206","description":"An issue was discovered in the rusb crate before 0.7.0 for Rust. Because of a lack of Send and Sync bounds, a data race and memory corruption can occur.","status":"published","published":"2021-01-22T09:06:59Z","modified":"2024-08-04T17:23:09.511Z","updated_at":"2026-11-02T14:35:55.128961Z"}],"euvd":[{"id":"EUVD-2021-1663","description":"An issue was discovered in the rusb crate before 0.7.0 for Rust. Because of a lack of Send and Sync bounds, a data race and memory corruption can occur.","status":"published","published":"2021-01-22T09:06:59Z","modified":"2024-08-04T17:23:09Z","updated_at":"2026-11-03T03:07:03.484914Z"}],"ghsa":[{"id":"GHSA-9mxw-4856-9cm5","title":"Data races in rusb","description":"Affected versions of rusb did not require UsbContext to implement Send and Sync. However, through Device and DeviceHandle it is possible to use UsbContexts across threads. This issue allows non-thread safe UsbContext types to be used concurrently leading to data races and memory corruption. The issue was fixed by adding Send and Sync bounds to UsbContext.","status":"published","published":"2021-08-25T20:50:51Z","modified":"2023-06-13T20:46:50Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-662","CWE-787"],"updated_at":"2026-11-02T14:36:54.225318Z"}],"nvd":[{"id":"CVE-2020-36206","description":"An issue was discovered in the rusb crate before 0.7.0 for Rust. Because of a lack of Send and Sync bounds, a data race and memory corruption can occur.","status":"published","published":"2021-01-26T18:15:55.77Z","modified":"2026-06-17T03:15:00.413Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":4.4,"vector":"AV:L/AC:M/Au:N/C:P/I:P/A:P","level":"medium","assessor":"primary"}],"cwes":["CWE-662","CWE-787"],"updated_at":"2026-11-02T14:06:30.596418Z"}],"osv":[{"id":"CVE-2020-36206","description":"An issue was discovered in the rusb crate before 0.7.0 for Rust. Because of a lack of Send and Sync bounds, a data race and memory corruption can occur.","status":"published","published":"2021-01-26T18:15:55.77Z","modified":"2026-10-24T10:30:19.901615167Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:16.612899Z"},{"id":"GHSA-9mxw-4856-9cm5","title":"Data races in rusb","description":"Affected versions of rusb did not require UsbContext to implement Send and Sync. However, through Device and DeviceHandle it is possible to use UsbContexts across threads. This issue allows non-thread safe UsbContext types to be used concurrently leading to data races and memory corruption. The issue was fixed by adding Send and Sync bounds to UsbContext.","status":"published","published":"2021-08-25T20:50:51Z","modified":"2023-11-08T04:03:41.476758Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-662","CWE-787"],"updated_at":"2026-11-02T15:46:43.875515Z"},{"id":"RUSTSEC-2020-0098","title":"UsbContext trait did not require implementers to be Send and Sync.","description":"Affected versions of `rusb` did not require `UsbContext` to implement `Send`\nand `Sync`. However, through `Device` and `DeviceHandle` it is possible to use\n`UsbContext`s across threads.\n\nThis issue allows non-thread safe `UsbContext` types to be used concurrently\nleading to data races and memory corruption.\n\nThe issue was fixed by adding `Send` and `Sync` bounds to `UsbContext`.","status":"published","published":"2020-12-18T12:00:00Z","modified":"2023-11-08T04:03:41.476758Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:39.492624Z"}]}}