{"id":"CVE-2020-36220","aliases":["EUVD-2021-1546","GHSA-3hj2-hh36-hv9v","RUSTSEC-2020-0114"],"status":"published","title":"Data race in va-ts","description":"An issue was discovered in the va-ts crate before 0.0.4 for Rust. Because Demuxer\u003cT\u003e omits a required T: Send bound, a data race and memory corruption can occur.","severity":{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-11","score":0.00811,"percentile":0.57378,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-662","CWE-667","CWE-787"],"published":"2020-12-22T12:00:00Z","modified":"2026-06-17T03:15:07Z","fixes":[{"ecosystem":"crates.io","package":"va-ts","fixed_in":["0.0.4"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"crates.io","package":"va-ts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.4"}]}]},{"source":"osv","ecosystem":"crates.io","package":"va-ts","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.4"}]}]},{"source":"osv","ecosystem":"crates.io","package":"va-ts","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"0.0.4"}]}]}],"products":[{"vendor":"va-ts_project","product":"va-ts"}],"references":[{"url":"https://rustsec.org/advisories/RUSTSEC-2020-0114.html","tags":["x_refsource_MISC","x_transferred","Exploit","Vendor Advisory","web","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-36220","tags":["advisory"]},{"url":"https://github.com/video-audio/va-ts/issues/4","tags":["web","report"]},{"url":"https://github.com/advisories/GHSA-3hj2-hh36-hv9v"},{"url":"https://github.com/video-audio/va-ts","tags":["package"]},{"url":"https://crates.io/crates/va-ts","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2020-36220","description":"An issue was discovered in the va-ts crate before 0.0.4 for Rust. Because Demuxer\u003cT\u003e omits a required T: Send bound, a data race and memory corruption can occur.","status":"published","published":"2021-01-22T09:03:48Z","modified":"2024-08-04T17:23:09.443Z","updated_at":"2026-11-02T14:35:54.80237Z"}],"euvd":[{"id":"EUVD-2021-1546","description":"An issue was discovered in the va-ts crate before 0.0.4 for Rust. Because Demuxer\u003cT\u003e omits a required T: Send bound, a data race and memory corruption can occur.","status":"published","published":"2021-01-22T09:03:48Z","modified":"2024-08-04T17:23:09Z","updated_at":"2026-11-03T03:07:03.484914Z"}],"ghsa":[{"id":"GHSA-3hj2-hh36-hv9v","title":"Data race in va-ts","description":"In the affected versions of this crate, Demuxer\u003cT\u003e unconditionally implemented Send with no trait bounds on T. This allows sending a non-Send type T across thread boundaries, which can cause undefined behavior like unlocking a mutex from a thread that didn't lock the mutex, or memory corruption from data race. The flaw was corrected in commit `0562cbf` by adding a T: Send bound to the Send impl for Demuxer\u003cT\u003e.","status":"published","published":"2021-08-25T20:51:56Z","modified":"2023-06-13T22:11:44Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-662","CWE-667","CWE-787"],"updated_at":"2026-11-02T14:36:54.225318Z"}],"nvd":[{"id":"CVE-2020-36220","description":"An issue was discovered in the va-ts crate before 0.0.4 for Rust. Because Demuxer\u003cT\u003e omits a required T: Send bound, a data race and memory corruption can occur.","status":"published","published":"2021-01-26T18:15:56.63Z","modified":"2026-06-17T03:15:07.95Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"},{"version":"2.0","score":4.3,"vector":"AV:N/AC:M/Au:N/C:N/I:N/A:P","level":"medium","assessor":"primary"}],"cwes":["CWE-662","CWE-667","CWE-787"],"updated_at":"2026-11-02T14:06:30.596418Z"}],"osv":[{"id":"GHSA-3hj2-hh36-hv9v","title":"Data race in va-ts","description":"In the affected versions of this crate, Demuxer\u003cT\u003e unconditionally implemented Send with no trait bounds on T. This allows sending a non-Send type T across thread boundaries, which can cause undefined behavior like unlocking a mutex from a thread that didn't lock the mutex, or memory corruption from data race. The flaw was corrected in commit `0562cbf` by adding a T: Send bound to the Send impl for Demuxer\u003cT\u003e.","status":"published","published":"2021-08-25T20:51:56Z","modified":"2023-11-08T04:03:42.2757Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-662","CWE-667","CWE-787"],"updated_at":"2026-11-02T15:46:35.747385Z"},{"id":"RUSTSEC-2020-0114","title":"`Demuxer` can carry non-Send types across thread boundaries","description":"In the affected versions of this crate, `Demuxer\u003cT\u003e` unconditionally implemented `Send` with no trait bounds on `T`.\n\nThis allows sending a non-Send type `T` across thread boundaries, which can cause undefined behavior like unlocking a mutex from a thread that didn't lock the mutex, or memory corruption from data race.\n\nThe flaw was corrected in commit 0562cbf by adding a `T: Send` bound to the `Send` impl for `Demuxer\u003cT\u003e`.","status":"published","published":"2020-12-22T12:00:00Z","modified":"2023-11-08T04:03:42.2757Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:53:39.492624Z"}]}}