9409 matches found
CVE-2020-35911
An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockReadGuard unsoundness...
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-35910
An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness...
UBUNTU-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...
UBUNTU-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...
UBUNTU-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-2018-25001
An issue was discovered in the libpulse-binding crate before 2.5.0 for Rust. proplist::Iterator can cause a use-after-free...
CVE-2018-25001
The CVE-2018-25001 issue affects the Rust crate libpulse-binding prior to version 2.5.0, where proplist::Iterator can cause a use-after-free by mismanaging the lifetime between Proplist and its iterator. Public references and advisories (e.g., GHSA-f56g-chqp-22m9 and GHSA-6GVC-4JVJ-PWQ4) describe...
CVE-2019-25001
CVE-2019-25001 affects the Rust crate serde_cbor prior to 0.10.2. The CBOR deserializer can cause stack consumption when processing nested semantic tags, enabling potential resource exhaustion. The issue is confined to the crate’s deserialization path; affected versions are those before 0.10.2. R...
CVE-2019-25002
The CVE-2019-25002 issue affects the sodiumoxide crate for Rust prior to version 0.2.5. The vulnerability stems from generichash::Digest::eq comparing the value to itself, producing degenerate security properties (reported across Red Hat, OSV, GHSA advisories, and NVD records). Practical impact i...
CVE-2019-25002
An issue was discovered in the sodiumoxide crate before 0.2.5 for Rust. generichash::Digest::eq compares itself to itself and thus has degenerate security properties...
CVE-2019-25003
CVE-2019-25003 affects the Rust libsecp256k1 crate prior to 0.3.1, where Scalar::check_overflow did not execute in constant time. This timing side-channel can allow an attacker to potentially obtain sensitive information. The issue is fixed in 0.3.1 by making Scalar::check_overflow constant time;...
CVE-2019-25004
CVE-2019-25004 affects the Rust crate flatbuffers prior to 0.6.1. The root cause is an implementation of impl Follow for bool that allows arbitrary bytes to be reinterpreted as a bool, defeating soundness. This could enable a remote attacker to bypass security restrictions by sending specially cr...
CVE-2019-25005
An issue was discovered in the chacha20 crate before 0.2.3 for Rust. A ChaCha20 counter overflow makes it easier for attackers to determine plaintext...
CVE-2019-25005
The CVE-2019-25005 issue affects the Rust chacha20 crate prior to 0.2.3. A 32‑bit ChaCha20 counter overflow can cause keystream repetition, making it easier for an attacker to determine plaintext. Public references describe the vulnerability and the fix: upgrading to version 0.2.3 (hot fix) where...
CVE-2019-25006
An issue was discovered in the streebog crate before 0.8.0 for Rust. The Streebog hash function can produce the wrong answer...
CVE-2019-25007
Summary : The vulnerability CVE-2019-25007 affects the Rust streebog crate prior to 0.8.0. Root cause : incorrect implementation of the internal update-sigma function, which could cause a panic for certain inputs. Impact : panics in the Streebog hash function; no exploit details are provided in t...
CVE-2019-25007
An issue was discovered in the streebog crate before 0.8.0 for Rust. The Streebog hash function can cause a panic...
CVE-2019-25009
CVE-2019-25009 — Rust http crate vulnerability : Affected component is the http crate (pre-0.1.20). The issue lies in the HeaderMap::Drain API, which can use a raw pointer, defeating soundness and potentially leading to memory-safety problems. This affects Rust projects depending on that crate. T...
