OMGeeky/advisory-db
1
0
Fork 0
mirror of https://github.com/OMGeeky/advisory-db.git synced 2025-12-30 00:03:57 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #693 from JOE1994/0057-async-coap

Browse Source 
async-coap: ArcGuard's Send and Sync should have bounds on RC
This commit is contained in:
Sergey "Shnatsel" Davidoff
2021-01-30 19:06:37 +01:00
committed by GitHub
parent a0c0baf2dd 064d4a4c6f
commit bd29fc0d7b
1 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
crates/async-coap/RUSTSEC-0000-0000.md Normal file
View File

@@ -0,0 +1,17 @@
```toml
[advisory]
id = "RUSTSEC-0000-0000"
package = "async-coap"
date = "2020-12-08"
url = "https://github.com/google/rust-async-coap/issues/33"
categories = ["memory-corruption"]
[versions]
patched = []
```
# ArcGuard's Send and Sync should have bounds on RC
Affected versions of this crate implement Send/Sync for `ArcGuard<RC, T>` with no trait bounds on `RC`. This allows users to send `RC: !Send` to other threads and also allows users to concurrently access `Rc: !Sync` from multiple threads.
This can result in memory corruption from data race or other undefined behavior caused by sending `T: !Send` to other threads (e.g. dropping `MutexGuard<T>` in another thread that didn't lock its mutex).