3511 matches found
CVE-2020-35905
The CVE-2020-35905 issue affects the futures-util crate for Rust (pre-0.3.7). A MutexGuard::map path can cause a data race in safe code under certain closure scenarios. This is a local issue in the crate’s synchronization logic that could lead to data races, as described in the advisory and Red H...
CVE-2020-35906
The CVE concerns the Rust futures-task crate before 0.3.6. The issue is a use-after-free in futures_task::waker when used with non-static types, potentially leading to memory safety problems. Affected software is the futures-task crate (Rust) prior to version 0.3.6; the root cause is not explicit...
CVE-2020-35906
An issue was discovered in the futures-task crate before 0.3.6 for Rust. futurestask::waker may cause a use-after-free in a non-static type situation...
CVE-2020-35906
An issue was discovered in the futures-task crate before 0.3.6 for Rust. futurestask::waker may cause a use-after-free in a non-static type situation...
CVE-2020-35907
An issue was discovered in the futures-task crate before 0.3.5 for Rust. futurestask::noopwakerref allows a NULL pointer dereference...
CVE-2020-35909
An issue was discovered in the multihash crate before 0.11.3 for Rust. The fromslice parsing code can panic via unsanitized data from a network server...
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-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-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-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-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-35915
An issue was discovered in the futures-intrusive crate before 0.4.0 for Rust. GenericMutexGuard allows cross-thread data races of non-Sync types...
CVE-2020-35916
The CVE-2020-35916 issue affects the Rust image crate, specifically versions before 0.23.12. The root cause is described as a Mutable reference having immutable provenance, with an example note that in LLVM IR the provenance may always be correct. The connected sources (NVD/OSS/Nessus/GHSA/Red Ha...
CVE-2020-35916
An issue was discovered in the image crate before 0.23.12 for Rust. A Mutable reference has immutable provenance. In the case of LLVM, the IR may be always correct...
CVE-2020-35916
An issue was discovered in the image crate before 0.23.12 for Rust. A Mutable reference has immutable provenance. In the case of LLVM, the IR may be always correct...