9840 matches found
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-35914
An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of RwLockWriteGuard unsoundness...
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...
CVE-2020-35914
The CVE-2020-35914 issue affects the Rust lock_api crate, specifically versions before 0.4.2. The root cause is a data race caused by unsoundness in RwLockWriteGuard. Impact is described as a data race condition; exploitation details are not provided in the supplied documents. Public references (...
CVE-2020-35915
CVE-2020-35915 affects the Rust futures-intrusive crate prior to 0.4.0. The issue is that GenericMutexGuard can allow cross-thread data races on non-Sync types due to how the guard tracks access to the locked data, potentially enabling unsafe concurrent access. The vulnerability is documented by ...
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-35917
CVE-2020-35917 affects the Rust pyo3 crate prior to 0.12.4 due to a reference-counting error and use-after-free in From<Py>. This can lead to incorrect reference handling and potential use-after-free. Impact details indicate partial availability impact (per CVSS) with local access, and reme...
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
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
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-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
CVE-2020-35921 — miow crate (Rust) Affected software: miow crate for Rust, prior to version 0.3.6. Root cause: incorrect assumptions about the memory layout of std::net::SocketAddr, leading to invalid memory handling. Impact: potential memory-safety issues due to misrepresentation of SocketAddr m...