3510 matches found
CVE-2020-35887
An issue was discovered in the arr crate through 2020-08-25 for Rust. There is a buffer overflow in Index and IndexMut...
CVE-2020-35888
An issue was discovered in the arr crate through 2020-08-25 for Rust. Uninitialized memory is dropped by Array::newfromtemplate...
CVE-2020-35888
The CVE-2020-35888 entry refers to the Rust arr crate (through 2020-08-25) with a bug where uninitialized memory is dropped by Array::new_from_template. NVD lists high severity (CVSSv2 7.5; CVSSv3.1 9.8) implying critical impact, network attack vector with low complexity and no authentication. Th...
CVE-2020-35889
An issue was discovered in the crayon crate through 2020-08-31 for Rust. A TOCTOU issue has a resultant memory safety violation via HandleLike...
CVE-2020-35890
The CVE-2020-35890 entry concerns the ordnung crate for Rust, where compact::Vec may violate memory safety via out-of-bounds access when handling large capacity. Related advisories describe additional memory-safety issues, including a remove() path that can double-free and out-of-bounds reads. Pu...
CVE-2020-35890
An issue was discovered in the ordnung crate through 2020-09-03 for Rust. compact::Vec violates memory safety via out-of-bounds access for large capacity...
CVE-2020-35891
CVE-2020-35891 concerns the Rust crate ordnung (up to version 0.0.1) where the type compact::Vec can violate memory safety due to a double-free during an emulated remove() operation. The issue is explicitly described as a memory-safety problem in compact::Vec, including a double-free scenario whe...
CVE-2020-35891
An issue was discovered in the ordnung crate through 2020-09-03 for Rust. compact::Vec violates memory safety via a remove double free...
CVE-2020-35892
CVE-2020-35892 : In Rust crate simple-slab , versions before 0.3.3 contain an out-of-bounds read in the index() function. The issue is corroborated by multiple sources (NVD, RH, GHSA/OSV) and is rated CRITICAL (CVSS3.1 base score 9.1; network interaction, no privileges required). The connected do...
CVE-2020-35894
An issue was discovered in the obstack crate before 0.1.4 for Rust. Unaligned references can occur...
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-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
An issue was discovered in the ws crate through 2020-09-25 for Rust. The outgoing buffer is not properly limited, leading to a remote memory-consumption attack...
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-35899
An issue was discovered in the actix-service crate before 1.0.6 for Rust. The Cell implementation allows obtaining more than one mutable reference to the same data...
CVE-2020-35901
An issue was discovered in the actix-http crate before 2.0.0-alpha.1 for Rust. There is a use-after-free in BodyStream...
CVE-2020-35902
An issue was discovered in the actix-codec crate before 0.3.0-beta.1 for Rust. There is a use-after-free in Framed...
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-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...