Rust advisories / va-ts
Vulnerability MediumRUSTSEC-2020-0114 · va-ts
RUSTSEC-2020-0114: `Demuxer` can carry non-Send types across thread boundaries
Short answerA security vulnerability in the va-ts crate: `Demuxer` can carry non-Send types across thread boundaries. Medium severity (CVSS 5.9). Fixed in 0.0.4: update to a fixed version.
| Crate | va-ts |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Before 0.0.4. |
| Fixed in | 0.0.4 |
| Severity | Medium, CVSS 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| Published | 2020-12-22 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36220, GHSA-3hj2-hh36-hv9v |
What to do
- See which version you have:
cargo tree -i va-ts(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p va-ts. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleva-ts = "0.0.4") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
In the affected versions of this crate, Demuxer<T> 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<T>.
References
- Package: crates.io/crates/va-ts
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0114.html
- Report: github.com/video-audio/va-ts/issues/4
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?