Files
advisory-db/crates/async-coap/RUSTSEC-2020-0124.md
2021-01-30 23:02:50 -05:00

18 lines
726 B
Markdown

```toml
[advisory]
id = "RUSTSEC-2020-0124"
package = "async-coap"
date = "2020-12-08"
url = "https://github.com/google/rust-async-coap/issues/33"
categories = ["memory-corruption", "thread-safety"]
[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).