CVE-2019-16137 Wrong memory orderings violates mutual exclusion in spin
A race condition in the Rust spin crate allows two writers to acquire a lock simultaneously, violating mutual exclusion and potentially causing data corruption.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2019-16137?
CVE-2019-16137 is a high-severity vulnerability in n/a, published on 9 Sep 2019. 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 spin crate before 0.5.2 for Rust, when RwLock is used. Because memory ordering is mishandled, two writers can acquire the lock at the same time, violating mutual exclusion.
Weakness: CWE-662
Which versions are affected by CVE-2019-16137?
3 open source packages ship an affected version, including spin. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
spin crates.io | All versions | 0.5.2 |
spin crates.io | All versions | 0.5.2 |
spin crates.io | From 0.0.0-0 | 0.5.2 |
Products include Spin-Rs Project Spin-Rs.
How do I fix CVE-2019-16137?
Upgrade spin to 0.5.2 or later.
Is CVE-2019-16137 being exploited?
There is no known exploitation of CVE-2019-16137 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2019-16137, GHSA-hv7x-f3pv-gpwr, RUSTSEC-2019-0013.