Rust advisories / scottqueue
Vulnerability HighRUSTSEC-2020-0133 · scottqueue
RUSTSEC-2020-0133: Queue<T> should have a Send bound on its Send/Sync traits
Short answerA security vulnerability in the scottqueue crate: Queue<T> should have a Send bound on its Send/Sync traits. High severity (CVSS 8.1). No fixed version: replace the crate or remove the affected code path.
| Crate | scottqueue |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Every version. |
| Fixed in | none |
| 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-15 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36453, GHSA-gvvv-w559-2hg6 |
What to do
- Find who pulls it in:
cargo tree -i scottqueue. - Avoid the affected API, or replace the crate.
Details from the advisory
Affected versions of this crate unconditionally implements Send/Sync for Queue<T>.
This allows (1) creating data races to a T: !Sync and (2) sending T: !Send to other threads, resulting in memory corruption or other undefined behavior.
References
- Package: crates.io/crates/scottqueue
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0133.html
- Report: github.com/rossdylan/rust-scottqueue/issues/1
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?