CVE-2020-36438 json
Data races in tiny_future
published 2020-12-08 5 y ago modified 2026-06-17 4 mo ago also GHSA-fg42-vwxx-xx5j , GHSA-m296-j53x-xv95 , RUSTSEC-2020-0118 , EUVD-2021-1699
- 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 tiny_future crate before 0.4.0 for Rust. Future<T> does not have bounds on its Send and Sync traits.
Patch / fix
- crates.io tiny_future 0.4.0
- tiny_future_project tiny_future 0.4.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 |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 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 | tiny_future | <0.4.0 >=0.0.0-0, <0.4.0 |
0.4.0 |
Classification
References
-
github.com
/KizzyCode/tiny_future/commit/7ab8a264980d23c2ed64e72f4636f38b7381eb39
web
-
github.com
/KizzyCode/tiny_future/commit/c7919199a0f6d1ce0e3c33499d1b37f862c990e4
web
-
github.com
/KizzyCode/tiny_future-rust/commit/c7919199a0f6d1ce0e3c33499d1b37f862c990e4
web
-
rustsec.org
/advisories/RUSTSEC-2020-0118.html
web, third-party-advisory, advisory
-
raw.githubusercontent.com
/rustsec/advisory-db/main/crates/tiny_future/RUSTSEC-2020-0118.md
web, third-party-advisory
-
github.com
/KizzyCode/tiny_future/issues/1
web, report
-
github.com
/KizzyCode/tiny_future
package
-
nvd.nist.gov
/vuln/detail/CVE-2020-36438
advisory
-
crates.io
/crates/tiny_future
package
Sources
- CVE List CVE-2020-36438
- GitHub Advisory GHSA-m296-j53x-xv95
- GitHub Advisory GHSA-fg42-vwxx-xx5j
- NVD CVE-2020-36438
- OSV RUSTSEC-2020-0118
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.