Rust advisories / may_queue
Vulnerability MediumRUSTSEC-2020-0111 · may_queue
RUSTSEC-2020-0111: may_queue's Queue lacks Send/Sync bound for its Send/Sync trait.
Short answerA security vulnerability in the may_queue crate: may_queue's Queue lacks Send/Sync bound for its Send/Sync trait.. Medium severity (CVSS 5.9). Fixed in 0.1.8: update to a fixed version.
| Crate | may_queue |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Before 0.1.8. |
| Fixed in | 0.1.8 |
| 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-11-10 |
| Last changed | 2024-10-25 |
| Also known as | CVE-2020-36217, GHSA-pphf-f93w-gc84 |
What to do
- See which version you have:
cargo tree -i may_queue(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p may_queue. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplemay_queue = "0.1.8") 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 may_queue implements Send/Sync for its Queue type without restricting it to Sendable types and Syncable types.
This allows non-Sync types such as Cell to be shared across threads leading to undefined behavior and memory corruption in concurrent programs.
References
- Package: crates.io/crates/may_queue
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0111.html
- Report: github.com/Xudong-Huang/may/issues/88
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?