2489 matches found
Design/Logic Flaw
An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockReadGuard unsoundness...
UBUNTU-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...
UBUNTU-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...
UBUNTU-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-35871
CVE-2020-35871 concerns the Rust package rusqlite prior to 0.23.0, where memory safety can be violated via a data race in the Auxdata API. Connected sources (RH CVE, OSV advisories, and EU/NVD references) consistently identify data races affecting rusqlite before version 0.23.0, including issues ...
CVE-2020-35876
An issue was discovered in the rio crate through 2020-05-11 for Rust. A struct can be leaked, allowing attackers to obtain sensitive information, cause a use-after-free, or cause a data race...
CVE-2020-35876
Removed by vendor...
CVE-2020-35876
The CVE-2020-35876 entry relates to the rio crate (Rust) where leaking a rio::Completion can prevent its drop code from running, enabling access to or dropping of the underlying I/O buffer. This can lead to use-after-free, data races, or leaking secrets. The primary technical details are document...
CVE-2020-35882
CVE-2020-35882 (rocket crate, Rust) : The issue affects the rocket crate prior to 0.4.5. LocalRequest::clone reuses the inner Request pointer and creates more than one mutable reference to the same object, which can lead to a data race in certain API usage. Public sources consistently describe th...
CVE-2020-35882
An issue was discovered in the rocket crate before 0.4.5 for Rust. LocalRequest::clone creates more than one mutable references to the same object, possibly causing a data race...
CVE-2020-35886
An issue was discovered in the arr crate through 2020-08-25 for Rust. An attacker can smuggle non-Sync/Send types across a thread boundary to cause a data race...
CVE-2020-35886
The CVE-2020-35886 issue concerns the arr crate (Rust) up to 2020-08-25. It describes a data race caused by smuggling non-Sync/Send types across a thread boundary, due to incorrect Sync/Send bounds. The connected records (NVD/NVD mirrors, Red Hat OSV/GHSA advisories, OSVGHSA entries) consistently...
CVE-2020-35897
An issue was discovered in the atom crate before 0.3.6 for Rust. An unsafe Send implementation allows a cross-thread data race...
CVE-2020-35897
The CVE-2020-35897 entry affects the Rust crate atom prior to version 0.3.6. The root cause is an unsafe Send implementation that permits cross‑thread data races, potentially enabling memory-safety issues. Documents from multiple sources (Red Hat, GitHub GHSA, OSV, NVD, RustSec advisories) corrob...
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-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-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...