RUSTSEC-2020-0149
on 2020-11-15: Data race and memory safety issue in
Index
Index
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 appendix
. Alternatively, you can download the tarball of appendix v0.2.2 or view the source online.
The
appendix
crate implements a key-value mapping data structure calledIndex<K, V>
that is stored on disk. The crate allows for any type to inhabit the genericK
andV
type parameters and implements Send and Sync for them unconditionally.Using a type that is not marked as
Send
orSync
withIndex
can allow it to be used across multiple threads leading to data races. Additionally using reference types for the keys or values will lead to the segmentation faults in the crate's code.CVE-2020-36469
GHSA-fvhr-7j8m-3cvc