mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2026-01-01 09:10:25 +01:00
Report 0027-libsbc to RustSec
This commit is contained in:
20
crates/libsbc/RUSTSEC-0000-0000.md
Normal file
20
crates/libsbc/RUSTSEC-0000-0000.md
Normal file
@@ -0,0 +1,20 @@
|
||||
```toml
|
||||
[advisory]
|
||||
id = "RUSTSEC-0000-0000"
|
||||
package = "libsbc"
|
||||
date = "2020-11-10"
|
||||
url = "https://github.com/mvertescher/libsbc-rs/issues/4"
|
||||
categories = ["memory-corruption"]
|
||||
informational = "unsound"
|
||||
|
||||
[versions]
|
||||
patched = [">= 0.1.5"]
|
||||
```
|
||||
|
||||
# Minor soundness issue with Decoder's Send trait
|
||||
|
||||
Affected versions of this crate implements `Send` for `Decoder<R>` for any `R: Read`. This allows to use `R: !Send` in `Decoder<R>` to send a non-Send type to another thread.
|
||||
|
||||
This can result in undefined behavior such as memory corruption from data race on `R`, or dropping `R = MutexGuard<_>` from a thread that didn't lock the mutex.
|
||||
|
||||
The flaw was corrected in commit a34d6e1 by adding trait bound `R: Send` to the `Send` impl for `Decoder<R>`.
|
||||
Reference in New Issue
Block a user