CVE-2020-36439 Data races in ticketed_lock
The ticketed_lock crate incorrectly implements Send for ticket types, potentially allowing data races in concurrent Rust applications.
- 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-36439?
CVE-2020-36439 is a high-severity vulnerability in n/a, published on 8 Aug 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 ticketed_lock crate before 0.3.0 for Rust. There are unconditional implementations of Send for ReadTicket<T> and WriteTicket<T>.
Weakness: CWE-362
Which versions are affected by CVE-2020-36439?
5 open source packages ship an affected version, including ticketed_lock. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
ticketed_lock crates.io | All versions | 0.3.0 |
ticketed_lock crates.io | All versions | 0.3.0 |
ticketed_lock crates.io | All versions | 0.3.0 |
ticketed_lock crates.io | All versions | 0.3.0 |
ticketed_lock crates.io | From 0.0.0-0 | 0.3.0 |
Products include Ticketed Lock Project Ticketed Lock.
How do I fix CVE-2020-36439?
Upgrade ticketed_lock to 0.3.0 or later.
Is CVE-2020-36439 being exploited?
There is no known exploitation of CVE-2020-36439 in the wild and no public exploit code.
Sources
Also known as GHSA-77m6-x95j-75r5, GHSA-gq4h-f254-7cw9, RUSTSEC-2020-0119.