CVE-2020-35892

An issue was discovered in the simple-slab crate before 0.3.3 for Rust. index allows an out-of-bounds read...

CVE-2020-35893

CVE-2020-35893 affects the Rust crate simple-slab, prior to version 0.3.3. The remove() function has an off-by-one error that can cause memory leakage and a drop of uninitialized memory. This is documented across multiple sources (NVD entry and OSV/GHSA advisories) and is not accompanied by publi...

CVE-2020-35894

CVE-2020-35894 affects the Rust crate obstack prior to 0.1.4. The underlying issue is unaligned references for types that require a large alignment, as described in the RustSec advisory (RUSTSEC-2020-0040). Reported through multiple feeds, this vulnerability is tied to the obstack crate’s handlin...

CVE-2020-35894

An issue was discovered in the obstack crate before 0.1.4 for Rust. Unaligned references can occur...

CVE-2020-35895

An issue was discovered in the stack crate before 0.3.1 for Rust. ArrayVec has an out-of-bounds write via element insertion...

CVE-2020-35895

The CVE-2020-35895 issue affects the Rust stack crate before 0.3.1, where ArrayVec insertion can trigger an out-of-bounds write due to a missing upper-bound check. The vulnerability is described across multiple sources (e.g., Rustsec/RUSTSEC-2020-0042 and related advisories) and is associated wit...

CVE-2020-35896

The CVE-2020-35896 issue affects the ws crate (Rust) where the outgoing buffer is not properly limited, allowing a remote memory‑consumption attack. Affected versions did not cap growth of the outgoing buffer, enabling a remote attacker to exhaust memory and kill the process on a single connectio...

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-35898

CVE-2020-35898 affects the actix-utils crate for Rust, prior to version 2.0.0. The root cause is a bespoke Cell implementation that does not properly track mutable references, allowing multiple mutable references to the same data. Impact: potential memory corruption or use-after-free scenarios; e...

CVE-2020-35899

CVE-2020-35899 concerns the actix-service crate for Rust prior to 1.0.6, where a bespoke Cell implementation may allow obtaining multiple mutable references to the same data. This root cause can enable use-after-free-like behavior and memory corruption. Several connected sources confirm the issue...

CVE-2020-35900

An issue was discovered in the array-queue crate through 2020-09-26 for Rust. A popback call may lead to a use-after-free...

CVE-2020-35900

CVE-2020-35900 affects the Rust array-queue crate (pop_back) and may cause a use-after-free due to incorrect indexing in the pop_back path. Multiple connected advisories (RUSTSEC-2020-0047, GHSA-75CQ-G75G-RXFF, OSV/RUSTSEC mirrors) describe the same issue. The available documents do not specify a...

CVE-2020-35901

CVE-2020-35901 affects the actix-http crate for Rust, with exploitation possible via a use-after-free in BodyStream caused by lack of pinning. The issue is tied to the crate’s handling of buffers and memory location, and is mitigated by upgrading to a fixed version (2.0.0-alpha.1) or later as ind...

CVE-2020-35902

CVE-2020-35902 affects the actix-codec crate prior to 0.3.0-beta.1 for Rust, with a use-after-free in Framed caused by lack of proper pinning. The issue is documented in RUSTSEC-2020-0049 and various feeds (Red Hat, OSV, GHSA). Impact is reflected in CVSS metrics (up to Critical in v3.1, HIGH in ...

CVE-2020-35903

CVE-2020-35903 affects the Rust dync crate prior to 0.5.0, where VecCopy can misalign elements because Vec may store non-u8 types. This enables misaligned access when reading/writing elements of different types. The issue is documented across multiple sources (e.g., RustSec/RUSTSEC-2020-0050 and ...

CVE-2020-35903

An issue was discovered in the dync crate before 0.5.0 for Rust. VecCopy allows misaligned element access because u8 is not always the type in question...

CVE-2020-35904

CVE-2020-35904 affects the Rust crate crossbeam-channel prior to version 0.4.4. The issue is an incorrect assumption about the relationship between memory allocation and the number of elements produced by an iterator, leading to unsound behavior when the Vec is reconstructed from a raw pointer ba...

CVE-2020-35904

An issue was discovered in the crossbeam-channel crate before 0.4.4 for Rust. It has incorrect expectations about the relationship between the memory allocation and how many iterator elements there are...

CVE-2020-35904

An issue was discovered in the crossbeam-channel crate before 0.4.4 for Rust. It has incorrect expectations about the relationship between the memory allocation and how many iterator elements there are...

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...