CVE-2019-16137 json
Wrong memory orderings violates mutual exclusion in spin
published 7y ago modified 4mo ago also GHSA-hv7x-f3pv-gpwr , RUSTSEC-2019-0013 , EUVD-2021-1759
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- crates.io spin 0.5.2
- spin-rs_project spin-rs 0.5.2
- rust-spin Debian 14, Debian 13, Debian 12 0.5.2-1
debian advisories DEBIAN-CVE-2019-16137
- github.com/mvdnes/spin-rs#66 pull request
Is CVE-2019-16137 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.42% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:N/I:N/A:C |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | spin | <0.5.2 >=0.0.0-0, <0.5.2 |
0.5.2 |
Classification
- Weakness
-
- CWE-662 Improper Synchronization
References
-
github.com
/mvdnes/spin-rs/pull/66
web
-
rustsec.org
/advisories/RUSTSEC-2019-0013.html
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-16137
advisory
-
github.com
/mvdnes/spin-rs/issues/65
web, report
-
github.com
/mvdnes/spin-rs
package
-
crates.io
/crates/spin
package
Sources
- CVE List CVE-2019-16137
- GitHub Advisory GHSA-hv7x-f3pv-gpwr
- NVD CVE-2019-16137
- OSV RUSTSEC-2019-0013
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.