HIGH8.1
GHSA-f6g6-54hm-fhxv
Data races in libsbc
Details
Affected versions of this crate implements `Send` for `Decoder<R>` for any `R: Read`. This allows `Decoder<R>` to contain `R: !Send` and carry (move) it 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>`.
Are you affected?
Enter the version of the package you're using.
Affected packages
crates.io/libsbc
Introduced in:
0Fixed in: 0.1.5Upgrade libsbc to 0.1.5 or newer (ecosystem crates.io).
References
- https://nvd.nist.gov/vuln/detail/CVE-2020-36440[ADVISORY]
- https://github.com/mvertescher/libsbc-rs/commit/a34d6e1[WEB]
- https://github.com/mvertescher/libsbc-rs[PACKAGE]
- https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/libsbc/RUSTSEC-2020-0120.md[WEB]
- https://rustsec.org/advisories/RUSTSEC-2020-0120.html[WEB]