Vulnerability Details : CVE-2019-16137
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.
Products affected by CVE-2019-16137
- cpe:2.3:a:spin-rs_project:spin-rs:*:*:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2019-16137
0.10%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 41 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2019-16137
| Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
|---|---|---|---|---|---|---|
|
7.8
|
HIGH | AV:N/AC:L/Au:N/C:N/I:N/A:C |
10.0
|
6.9
|
NIST | |
|
7.5
|
HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
3.9
|
3.6
|
NIST |
CWE ids for CVE-2019-16137
-
The product utilizes multiple threads or processes to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes.Assigned by: nvd@nist.gov (Primary)
References for CVE-2019-16137
-
https://rustsec.org/advisories/RUSTSEC-2019-0013.html
RUSTSEC-2019-0013: spin: Wrong memory orderings in RwLock potentially violates mutual exclusion › RustSec Advisory DatabaseThird Party Advisory
Jump to