OMGeeky/advisory-db
1
0
Fork 0
mirror of https://github.com/OMGeeky/advisory-db.git synced 2026-01-20 02:21:00 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #632 from RustSec/assign-ids

Browse Source 
Assigned RUSTSEC-2020-0107 to hashconsing, RUSTSEC-2020-0108 to eventio, RUSTSEC-2020-0109 to stderr, RUSTSEC-2020-0110 to may_queue, RUSTSEC-2020-0111 to buttplug
This commit is contained in:
Sergey "Shnatsel" Davidoff
2021-01-20 20:29:24 +01:00
committed by GitHub
parent 645376911b 699c1de232
commit 84badb657b
2 changed files with 22 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
crates/buttplug/RUSTSEC-2020-0111.md Normal file
View File

@@ -0,0 +1,21 @@
```toml
[advisory]
id = "RUSTSEC-2020-0111"
package = "buttplug"
date = "2020-12-18"
url = "https://github.com/buttplugio/buttplug-rs/issues/225"
categories = ["memory-corruption"]
[versions]
# Versions which include fixes for this vulnerability
patched = [">= 1.0.4"]
```
# ButtplugFutureStateShared allows data race to (!Send|!Sync) objects
`ButtplugFutureStateShared<T>` implements `Send` & `Sync` regardless of `T`.
If `T: !Send` for `ButtplugFutureStateShared<T>`, it is possible to move non-Send types across thread boundaries (e.g. `T`=`Rc<T>`) and lead to undefined behavior.
If `T: !Sync` for `ButtplugFutureStateShared<T>`, it is possible to cause data race to `T` (e.g. `T`=`Arc<Cell<_>>`) and lead to undefined behavior.
The flaw was corrected in version 1.0.4 by removing manual implementations of `Send`/`Sync` for `ButtplugFutureStateShared<T>` to let rustc generate auto trait implementations with correct trait bounds on `T`.

2
crates/may_queue/RUSTSEC-0000-0000.md → crates/may_queue/RUSTSEC-2020-0110.md
View File

@@ -1,6 +1,6 @@
```toml
[advisory]
id = "RUSTSEC-0000-0000"
id = "RUSTSEC-2020-0110"
package = "may_queue"
date = "2020-11-10"
url = "https://github.com/Xudong-Huang/may/issues/88"