RUSTSEC-2020-0124
on 2020-12-08: ArcGuard's Send and Sync should have bounds on RC
This crate has no reviews yet. To add a review, set up your cargo-crev
.
Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories. There is absolutely no guarantee that the repository URL declared by the crate belongs to the crate, or that the code in the repository is the code inside the published tarball.
To review the actual code of the crate, it's best to use cargo crev open async-coap
. Alternatively, you can download the tarball of async-coap v0.1.0 or view the source online.
Affected versions of this crate implement Send/Sync for
ArcGuard<RC, T>
with no trait bounds onRC
. This allows users to sendRC: !Send
to other threads and also allows users to concurrently accessRc: !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. droppingMutexGuard<T>
in another thread that didn't lock its mutex).CVE-2020-36444
GHSA-9j8q-m9x5-9g6j