From 92a9ea5f212220b466bb690a2646526e942ce805 Mon Sep 17 00:00:00 2001
From: JOE1994 <joseph942010@gmail.com>
Date: Sun, 24 Jan 2021 16:13:12 -0500
Subject: [PATCH] Report 0032-conqueue to RustSec

---
 crates/conqueue/RUSTSEC-0000-0000.md | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
 create mode 100644 crates/conqueue/RUSTSEC-0000-0000.md

diff --git a/crates/conqueue/RUSTSEC-0000-0000.md b/crates/conqueue/RUSTSEC-0000-0000.md
new file mode 100644
index 0000000..76c544e
--- /dev/null
+++ b/crates/conqueue/RUSTSEC-0000-0000.md
@@ -0,0 +1,20 @@
+```toml
+[advisory]
+id = "RUSTSEC-0000-0000"
+package = "conqueue"
+date = "2020-11-24"
+url = "https://github.com/longshorej/conqueue/issues/9"
+categories = ["memory-corruption"]
+
+[versions]
+patched = [">= 0.4.0"]
+```
+
+# QueueSender<T>/QueueReceiver<T>: Send/Sync impls need `T: Send`
+
+Affected versions of this crate unconditionally implemented `Send`/`Sync` for `QueueSender<T>`,
+allowing to send non-Send `T` to other threads by invoking `(&QueueSender<T>).send()`.
+
+This fails to prevent users from creating data races by sending types like `Rc<T>` or `Arc<Cell<T>>` to other threads, which can lead to memory corruption.
+
+The flaw was corrected in commit 1e462c3 by imposing `T: Send` to both `Send`/`Sync` impls for `QueueSender<T>`/`QueueReceiver<T>`.