60 matches found
CVE-2020-35910
CVE-2020-35910 affects the Rust crate lock_api prior to version 0.4.2. The issue is a data race caused by unsoundness in MappedMutexGuard, as reported across multiple sources referencing the same flaw in lock_api. This can enable data races in affected code paths that rely on the lock. The vulner...
CVE-2020-35910
An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness...
CVE-2020-35910
An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness...
CVE-2020-35911
CVE-2020-35911 affects the Rust lock_api crate prior to 0.4.2. The issue is a data race caused by unsoundness in MappedRwLockReadGuard, with no explicit exploit details provided. Remediation: upgrade to 0.4.2 or later. Details are limited to the provided documents.
CVE-2020-35911
An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockReadGuard unsoundness...
CVE-2020-35911
An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockReadGuard unsoundness...
CVE-2020-35912
An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness...
CVE-2020-35912
An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness...
CVE-2020-35912
CVE-2020-35912 affects the Rust lock_api crate prior to 0.4.2, where a data race can occur due to unsoundness in MappedRwLockWriteGuard. The connected records corroborate the vulnerability text but do not provide explicit exploitation details, affected products beyond the Rust crate, or a stated ...
CVE-2020-35913
An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness...
CVE-2020-35913
CVE-2020-35913 concerns the Rust crate lock_api (pre-0.4.2). The issue is a data race caused by unsoundness in RwLockReadGuard , as documented across multiple sources in the connected set (e.g., Red Hat advisory and OSV entries). Affected component: the lock_api crate before version 0.4.2. Impact...
CVE-2020-35913
An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness...
CVE-2020-35914
The CVE-2020-35914 issue affects the Rust lock_api crate, specifically versions before 0.4.2. The root cause is a data race caused by unsoundness in RwLockWriteGuard. Impact is described as a data race condition; exploitation details are not provided in the supplied documents. Public references (...
CVE-2020-35914
An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of RwLockWriteGuard unsoundness...
CVE-2020-35914
An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of RwLockWriteGuard unsoundness...
Rust lock_api crate security vulnerability
Rust is a general-purpose, compiled programming language from the Mozilla Foundation. A security vulnerability exists in lockapi crate before 0.4.2 for Rust, which has an unsound MappedMutexGuard and may allow data contention...
Some lock_api lock guard objects can cause data races
Affected versions of lockapi 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...
RUSTSEC-2020-0070 Some lock_api lock guard objects can cause data races
Affected versions of lockapi 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...
RUSTSEC-2019-0031 spin is no longer actively maintained
The author of the spin crate does not have time or interest to maintain it. Consider the following alternatives all of which support nostd: - conquer-once - lockapi a subproject of parkinglot - spinningtop spinlock crate built on lockapi - spinning...
spin is no longer actively maintained
The author of the spin crate does not have time or interest to maintain it. Consider the following alternatives all of which support nostd: - conquer-once - lockapi a subproject of parkinglot - spinningtop spinlock crate built on lockapi - spinning...