mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2025-12-27 06:29:31 +01:00
Add advisory for data race in tiny_future
This commit is contained in:
23
crates/tiny_future/RUSTSEC-0000-0000.md
Normal file
23
crates/tiny_future/RUSTSEC-0000-0000.md
Normal file
@@ -0,0 +1,23 @@
|
||||
```toml
|
||||
[advisory]
|
||||
id = "RUSTSEC-0000-0000"
|
||||
package = "tiny_future"
|
||||
date = "2020-12-08"
|
||||
url = "https://github.com/KizzyCode/tiny_future/issues/1"
|
||||
categories = ["memory-corruption"]
|
||||
keywords = ["concurrency"]
|
||||
|
||||
[versions]
|
||||
patched = [">= 0.4.0"]
|
||||
```
|
||||
|
||||
# Future<T> lacks bounds on Send and Sync.
|
||||
|
||||
`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`.
|
||||
Reference in New Issue
Block a user