9840 matches found
CVE-2020-35905
An issue was discovered in the futures-util crate before 0.3.7 for Rust. MutexGuard::map can cause a data race for certain closure situations in safe code...
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
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-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-35907
The CVE-2020-35907 entry concerns the Rust futures-task crate prior to 0.3.5. The issue, in futures_task::noop_waker_ref, permits a NULL pointer dereference, potentially causing a crash. Affected component: futures-task crate before 0.3.5. Impact statements are limited to what is stated; no explo...
CVE-2020-35908
An issue was discovered in the futures-util crate before 0.3.2 for Rust. FuturesUnordered can lead to data corruption because Sync is mishandled...
CVE-2020-35908
CVE-2020-35908 affects the Rust crate futures-util (before 0.3.2). The issue is an improper implementation of Sync in the FuturesUnordered structure, which used interior mutability via a Cell without proper synchronization. This can lead to data corruption when multiple threads access the interna...
CVE-2020-35909
The CVE-2020-35909 issue affects the Rust multihash crate prior to 0.11.3. The from_slice (and from_bytes) parsing path can panic when fed certain malformed or unsanitized input from a network source, potentially enabling DoS via unexpected panics in network code. Connected advisories (e.g., rust...
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
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
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
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-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-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-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...