RUSTSEC-2020-0140
(unsound)
on 2020-11-10:
Shared
can cause a data race
Shared
can cause a data race
This crate has no reviews yet. To add a review, set up your cargo-crev
.
Lib.rs has been able to verify that all files in the crate's tarball are in the crate's repository. Please note that this check is still in beta, and absence of this confirmation does not mean that the files don't match.
Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories, so there is a possibility that published crates have a misleading repository URL, or contain different code from the code in the repository.
To review the actual code of the crate, it's best to use cargo crev open model
. Alternatively, you can download the tarball of model v0.1.2 or view the source online.
Shared
data structure inmodel
crate implementsSend
andSync
traits regardless of the inner type. This allows safe Rust code to trigger a data race, which is undefined behavior in Rust.Users are advised to treat
Shared
as an unsafe type. It should not be used outside of the testing context, and care must be taken so that the testing code does not have a data race besides a race condition that is expected to be caught by the test.Check the Rustonomicon for the difference between a data race and a general race condition.
CVE-2020-36460
GHSA-mxv6-q98x-h958