3843 matches found
CVE-2020-35869
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because rusqlite::trace::log mishandles format strings...
CVE-2020-35871
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via an Auxdata API data race...
CVE-2020-35871
CVE-2020-35871 concerns the Rust package rusqlite prior to 0.23.0, where memory safety can be violated via a data race in the Auxdata API. Connected sources (RH CVE, OSV advisories, and EU/NVD references) consistently identify data races affecting rusqlite before version 0.23.0, including issues ...
CVE-2020-35872
The CVE-2020-35872 entry concerns the rusqlite crate for Rust, before version 0.23.0. The root cause is a memory-safety issue exposed via the repr(Rust) type, which can lead to memory-safety violations. The vulnerability is reflected in high-severity CVSS scores (NVD: CVSS2 7.5; CVSS3.1 9.8) with...
CVE-2020-35874
CVE-2020-35874 relates to the Rust internment crate; ArcIntern::drop has a race that can lead to use-after-free. Affected: internment up to versions before 0.3.12. Impact: potential memory safety issue. Mitigation: upgrade to 0.3.12 or later, as the fix serializes access during deallocation. Othe...
CVE-2020-35874
An issue was discovered in the internment crate through 2020-05-28 for Rust. ArcIntern::drop has a race condition and resultant use-after-free...
CVE-2020-35876
The CVE-2020-35876 entry relates to the rio crate (Rust) where leaking a rio::Completion can prevent its drop code from running, enabling access to or dropping of the underlying I/O buffer. This can lead to use-after-free, data races, or leaking secrets. The primary technical details are document...
CVE-2020-35876
Removed by vendor...
CVE-2020-35876
An issue was discovered in the rio crate through 2020-05-11 for Rust. A struct can be leaked, allowing attackers to obtain sensitive information, cause a use-after-free, or cause a data race...
CVE-2020-35877
CVE-2020-35877 affects the Rust ozone crate (up to version 0.1.0) with memory-safety violations caused by out-of-bounds access. Documents consistently describe an out-of-bounds read/write risk but do not provide concrete exploit details or a stated fixed version. Remediation/fixes are not specifi...
CVE-2020-35877
An issue was discovered in the ozone crate through 2020-07-04 for Rust. Memory safety is violated because of out-of-bounds access...
CVE-2020-35878
An issue was discovered in the ozone crate through 2020-07-04 for Rust. Memory safety is violated because of the dropping of uninitialized memory...
CVE-2020-35878
The CVE-2020-35878 issue affects the Rust Ozone crate (up to 2020-07-04). Reported memory safety violations involve dropping uninitialized memory, with other sources noting out-of-bounds access in ozone. Public references (NVD entry, RH advisory, OSV/RUSTSEC) describe the vulnerability as memory ...
CVE-2020-35879
An issue was discovered in the rulinalg crate through 2020-02-11 for Rust. There are incorrect lifetime-boundary definitions for RowMut::rawslice and RowMut::rawslicemut...
CVE-2020-35880
An issue was discovered in the bigint crate through 2020-05-07 for Rust. It allows a soundness violation...
CVE-2020-35880
The CVE-2020-35880 entry relates to the Rust bigint crate (pre-2020-05-07). The connected advisories describe an unsoundness in bigint, i.e., a soundness violation in the implementation. Practical impact and exploit details are not provided in the supplied documents; they only state there is a so...
CVE-2020-35881
An issue was discovered in the traitobject crate through 2020-06-01 for Rust. It has false expectations about fat pointers, possibly causing memory corruption in, for example, Rust 2.x...
CVE-2020-35881
CVE-2020-35881 affects the traitobject crate in Rust (through 2020-06-01). The issue stems from incorrect fat-pointer layout assumptions, potentially causing out-of-bounds writes and memory corruption (also described in related advisories such as GHSA-J79J-CX3H-G27H).
CVE-2020-35882
CVE-2020-35882 (rocket crate, Rust) : The issue affects the rocket crate prior to 0.4.5. LocalRequest::clone reuses the inner Request pointer and creates more than one mutable reference to the same object, which can lead to a data race in certain API usage. Public sources consistently describe th...