CVE-2020-36439 json
Duplicate Advisory: Data races in ticketed_lock
published 2020-11-17 5 y ago modified 2026-06-17 4 mo ago also GHSA-77m6-x95j-75r5 , GHSA-gq4h-f254-7cw9 , RUSTSEC-2020-0119 , EUVD-2021-1612
- cvss
- 8.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
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>.
Patch / fix
- crates.io ticketed_lock 0.3.0
- ticketed_lock_project ticketed_lock 0.3.0
Exploit prediction
0.77% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| OSV | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | ticketed_lock | <0.3.0 >=0.0.0-0, <0.3.0 |
0.3.0 |
Classification
References
-
github.com
/kvark/ticketed_lock/commit/a986a9335d591fa5c826157d1674d47aa525357f
web
-
rustsec.org
/advisories/RUSTSEC-2020-0119.html
web, third-party-advisory, advisory
-
raw.githubusercontent.com
/rustsec/advisory-db/main/crates/ticketed_lock/RUSTSEC-2020-0119.md
web, third-party-advisory
-
github.com
/kvark/ticketed_lock/issues/7
web, report
-
nvd.nist.gov
/vuln/detail/CVE-2020-36439
advisory
-
github.com
/kvark/ticketed_lock
web
-
crates.io
/crates/ticketed_lock
package
Sources
- CVE List CVE-2020-36439
- GitHub Advisory GHSA-gq4h-f254-7cw9
- GitHub Advisory GHSA-77m6-x95j-75r5
- NVD CVE-2020-36439
- OSV RUSTSEC-2020-0119
Fencer Vulns 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.