Data races in tiny_future
Priority LOW 38CWE-362Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
`tiny_future` contains a light-weight implementation of `Future`s. The `Future` type it has lacked bound on its `Send` and `Sync` traits. This allows for a bug where non-thread safe types such as `Cell` can be used in `Future`s and cause data races in concurrent programs. The flaw was corrected in commit `c791919` by adding trait bounds to `Future`'s `Send` and `Sync`.
Why it matters now
Fix Fixed tiny_future (crates.io): 0.4.0
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | tiny_future (crates.io) | before 0.4.0 | 0.4.0 | Patch available | GHSA-m296-j53x-xv95 |
- tiny_future (crates.io) Vendor— Affected before 0.4.0 Fixed in 0.4.0 Patch available GHSA-m296-j53x-xv95
Remediation
- Fix · GHSA-m296-j53x-xv95 tiny_future (crates.io) Fixed in 0.4.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-m296-j53x-xv95
References
Other 5
- https://github.com/KizzyCode/tiny_future/issues/1
- https://github.com/KizzyCode/tiny_future/commit/7ab8a264980d23c2ed64e72f4636f38b7381eb39
- https://github.com/KizzyCode/tiny_future/commit/c7919199a0f6d1ce0e3c33499d1b37f862c990e4
- https://github.com/KizzyCode/tiny_future
- https://rustsec.org/advisories/RUSTSEC-2020-0118.html
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences