—
RUSTSEC-2020-0070
Some lock_api lock guard objects can cause data races
Details
Affected versions of lock_api had unsound implementations of the `Send` or `Sync` traits for some guard objects, namely:
* MappedMutexGuard * MappedRwLockReadGuard * MappedRwLockWriteGuard * RwLockReadGuard * RwLockWriteGuard
These guards could allow data races through types that are not safe to `Send` across thread boundaries in safe Rust code.
This issue was fixed by changing the trait bounds on the `Mapped` guard types and removing the `Sync` trait for the `RwLock` guards.
Are you affected?
Enter the version of the package you're using.
Affected packages
crates.io/lock_api
Introduced in:
0.0.0-0Fixed in: 0.4.2Upgrade lock_api to 0.4.2 or newer (ecosystem crates.io).