3843 matches found
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...
CVE-2020-35917
An issue was discovered in the pyo3 crate before 0.12.4 for Rust. There is a reference-counting error and use-after-free in From...
CVE-2020-35918
An issue was discovered in the branca crate before 0.10.0 for Rust. Decoding tokens with invalid base62 data can panic...
CVE-2020-35918
The CVE-2020-35918 entry concerns the branca crate for Rust. Affected component: Branco token decoding function when given invalid base62 data. Root cause: decoding tokens with incorrect base62 encoding can trigger a panic (unhandled exception) in versions prior to 0.10.0. Impact: runtime panic t...
CVE-2020-35919
An issue was discovered in the net2 crate before 0.2.36 for Rust. It has false expectations about the std::net::SocketAddr memory representation...
CVE-2020-35919
CVE-2020-35919 affects the Rust net2 crate prior to 0.2.36. Root cause: the crate makes false assumptions about the memory layout of std::net::SocketAddr, casting pointers to the system sockaddr representation. This can lead to invalid memory access if the standard library layout changes. The iss...
CVE-2020-35919
An issue was discovered in the net2 crate before 0.2.36 for Rust. It has false expectations about the std::net::SocketAddr memory representation...
CVE-2020-35920
The CVE-2020-35920 entry concerns the Rust socket2 crate (before 0.3.16) that makes incorrect assumptions about the memory layout of std::net::SocketAddr. This mismatch can lead to invalid memory handling when converting between Rust socket addresses and system representations, potentially causin...
CVE-2020-35920
An issue was discovered in the socket2 crate before 0.3.16 for Rust. It has false expectations about the std::net::SocketAddr memory representation...
CVE-2020-35920
An issue was discovered in the socket2 crate before 0.3.16 for Rust. It has false expectations about the std::net::SocketAddr memory representation...
CVE-2020-35921
An issue was discovered in the miow crate before 0.3.6 for Rust. It has false expectations about the std::net::SocketAddr memory representation...
CVE-2020-35921
An issue was discovered in the miow crate before 0.3.6 for Rust. It has false expectations about the std::net::SocketAddr memory representation...
CVE-2020-35922
An issue was discovered in the mio crate before 0.7.6 for Rust. It has false expectations about the std::net::SocketAddr memory representation...
CVE-2020-35922
An issue was discovered in the mio crate before 0.7.6 for Rust. It has false expectations about the std::net::SocketAddr memory representation...
CVE-2020-35922
The CVE-2020-35922 issue affects the Rust mio crate prior to 0.7.6, where the component makes false assumptions about the memory representation of std::net::SocketAddr. This root cause stems from assuming SocketAddrV4/V6 share a memory layout with the system sockaddr, leading to unsafe casts and ...
CVE-2020-35924
CVE-2020-35924 affects the Rust crate try-mutex prior to 0.3.0. The issue arises because TryMutex allowed cross-thread sending of non-Send types due to an unconditional Sync implementation, enabling data races. The root cause is absence of a Send bound on the Sync trait implementation for TryMute...
CVE-2020-35925
Summary (concrete details): The issue CVE-2020-35925 affects the Rust magnetic crate up to version 2.0.1. The root cause: MPMCConsumer and MPMCProducer implementations unconditionally provided Sync/Send, allowing cross-thread sending of non-Send types. This creates a potential data race. The flaw...