Search Results (363005 CVEs found)

CVE Vendors Products Updated CVSS v3.1
CVE-2020-35923 1 Ordered-float Project 1 Ordered-float 2024-11-21 5.5 Medium
An issue was discovered in the ordered-float crate before 1.1.1 and 2.x before 2.0.1 for Rust. A NotNan value can contain a NaN.
CVE-2020-35922 1 Mio Project 1 Mio 2024-11-21 5.5 Medium
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-35921 1 Miow Project 1 Miow 2024-11-21 5.5 Medium
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-35920 1 Rust-lang 1 Socket2 2024-11-21 5.5 Medium
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-35919 1 Net2 Project 1 Net2 2024-11-21 5.5 Medium
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-35918 1 Hakobaito 1 Branca 2024-11-21 5.5 Medium
An issue was discovered in the branca crate before 0.10.0 for Rust. Decoding tokens (with invalid base62 data) can panic.
CVE-2020-35917 1 Pyo3 Project 1 Pyo3 2024-11-21 5.5 Medium
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<Py<T>>.
CVE-2020-35916 1 Image-rs 1 Image 2024-11-21 5.5 Medium
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-35915 1 Futures-intrusive Project 1 Futures-intrusive 2024-11-21 5.5 Medium
An issue was discovered in the futures-intrusive crate before 0.4.0 for Rust. GenericMutexGuard allows cross-thread data races of non-Sync types.
CVE-2020-35914 1 Lock Api Project 1 Lock Api 2024-11-21 4.7 Medium
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockWriteGuard unsoundness.
CVE-2020-35913 1 Lock Api Project 1 Lock Api 2024-11-21 4.7 Medium
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness.
CVE-2020-35912 1 Lock Api Project 1 Lock Api 2024-11-21 4.7 Medium
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness.
CVE-2020-35911 1 Lock Api Project 1 Lock Api 2024-11-21 4.7 Medium
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockReadGuard unsoundness.
CVE-2020-35910 1 Lock Api Project 1 Lock Api 2024-11-21 5.5 Medium
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness.
CVE-2020-35909 1 Protocol 1 Multihash 2024-11-21 7.5 High
An issue was discovered in the multihash crate before 0.11.3 for Rust. The from_slice parsing code can panic via unsanitized data from a network server.
CVE-2020-35908 1 Rust-lang 1 Future-utils 2024-11-21 5.5 Medium
An issue was discovered in the futures-util crate before 0.3.2 for Rust. FuturesUnordered can lead to data corruption because Sync is mishandled.
CVE-2020-35907 1 Rust-lang 1 Futures-task 2024-11-21 5.5 Medium
An issue was discovered in the futures-task crate before 0.3.5 for Rust. futures_task::noop_waker_ref allows a NULL pointer dereference.
CVE-2020-35905 1 Rust-lang 1 Future-utils 2024-11-21 4.7 Medium
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-35904 1 Crossbeam-channel Project 1 Crossbeam-channel 2024-11-21 5.5 Medium
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-35903 1 Dync Project 1 Dync 2024-11-21 5.5 Medium
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.