Vulnerability Details : CVE-2020-36439
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>.
Products affected by CVE-2020-36439
- cpe:2.3:a:ticketed_lock_project:ticketed_lock:*:*:*:*:*:rust:*:*
Exploit prediction scoring system (EPSS) score for CVE-2020-36439
0.34%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 53 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2020-36439
| Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
|---|---|---|---|---|---|---|
|
6.8
|
MEDIUM | AV:N/AC:M/Au:N/C:P/I:P/A:P |
8.6
|
6.4
|
NIST | |
|
8.1
|
HIGH | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
2.2
|
5.9
|
NIST |
CWE ids for CVE-2020-36439
-
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.Assigned by: nvd@nist.gov (Primary)
References for CVE-2020-36439
-
https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/ticketed_lock/RUSTSEC-2020-0119.md
Third Party Advisory
-
https://rustsec.org/advisories/RUSTSEC-2020-0119.html
RUSTSEC-2020-0119: ticketed_lock: ReadTicket and WriteTicket should only be sendable when T is Send › RustSec Advisory DatabaseThird Party Advisory
Jump to