CVE-2019-16137
HIGH
7.5
CVSS Score
Published: September 9, 2019 at 11:45 AM UTC
Updated: June 17, 2026 at 02:21 AM UTC
1 product affected across 1 vendorSpin Rs
Using N/A by N/A?
Get instant alerts when new vulnerabilities affect N/A - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 1%
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.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
v < 0.5.2
Affected range stops below 0.5.2, so it looks safe — our inference, not a vendor statement
Remediation
No guide yetNo remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.
References (1)
x_refsource_MISCThird Party Advisory
Source: [email protected]
https://rustsec.org/advisories/RUSTSEC-2019-0013.htmlCVSS
- Attack Vector
- NETWORK
- Complexity
- LOW
- Privileges
- NONE
- User Interaction
- NONE
- Scope
- UNCHANGED
- Confidentiality
- NONE
- Integrity
- NONE
- Availability
- HIGH
Vector?
Quick Info
StatusMODIFIED
CWE
CWE-662
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card