Rust advisories / ticketed_lock
Vulnerability HighRUSTSEC-2020-0119 · ticketed_lock
RUSTSEC-2020-0119: ReadTicket and WriteTicket should only be sendable when T is Send
Short answerA security vulnerability in the ticketed_lock crate: ReadTicket and WriteTicket should only be sendable when T is Send. High severity (CVSS 8.1). Fixed in 0.3.0: update to a fixed version.
| Crate | ticketed_lock |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Before 0.3.0. |
| Fixed in | 0.3.0 |
| Severity | High, CVSS 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Published | 2020-11-17 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36439, GHSA-77m6-x95j-75r5, GHSA-gq4h-f254-7cw9 |
What to do
- See which version you have:
cargo tree -i ticketed_lock(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p ticketed_lock. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleticketed_lock = "0.3.0") 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
Affected versions of this crate unconditionally implemented Send for ReadTicket<T> & WriteTicket<T>. This allows to send non-Send T to other threads.
This can allows creating data races by cloning types with internal mutability and sending them to other threads (as T of ReadTicket<T>/WriteTicket<T>). Such data races can cause memory corruption or other undefined behavior.
The flaw was corrected in commit a986a93 by adding T: Send bounds to Send impls of ReadTicket<T>/WriteTicket<T>.
References
- Package: crates.io/crates/ticketed_lock
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0119.html
- Report: github.com/kvark/ticketed_lock/issues/7
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?