CVE-2020-36217 Data race in may_queue
A memory corruption vulnerability in the Rust may_queue crate allows attackers to potentially execute arbitrary code or cause denial of service due to missing thread-safety bounds.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2020-36217?
CVE-2020-36217 is a medium-severity memory corruption vulnerability in n/a, published on 22 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
An issue was discovered in the may_queue crate through 2020-11-10 for Rust. Because Queue does not have bounds on its Send trait or Sync trait, memory corruption can occur.
Which versions are affected by CVE-2020-36217?
3 open source packages ship an affected version, including may_queue. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
may_queue crates.io | All versions to 0.1.8 | None |
may_queue crates.io | All versions to 0.1.8 | None |
may_queue crates.io | From 0.0.0-0 | 0.1.8 |
Products include May Queue Project May Queue.
How do I fix CVE-2020-36217?
Upgrade may_queue to 0.1.8 or later.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2020-36217 being exploited?
There is no known exploitation of CVE-2020-36217 in the wild and no public exploit code.
Sources
Also known as GHSA-pphf-f93w-gc84, RUSTSEC-2020-0111.