2495 matches found
CVE-2020-36207
An issue was discovered in the aovec crate through 2020-12-10 for Rust. Because Aovec does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur...
CVE-2020-36206
An issue was discovered in the rusb crate before 0.7.0 for Rust. Because of a lack of Send and Sync bounds, a data race and memory corruption can occur...
CVE-2020-36209
An issue was discovered in the late-static crate before 0.4.0 for Rust. Because Sync is implemented for LateStatic with T: Send, a data race can occur...
Memory corruption
An issue was discovered in the aovec crate through 2020-12-10 for Rust. Because Aovec does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur...
Design/Logic Flaw
An issue was discovered in the multiqueue2 crate before 0.1.7 for Rust. Because a non-Send type can be sent to a different thread, a data race can occur...
Memory corruption
An issue was discovered in Input in the eventio crate before 0.5.1 for Rust. Because a non-Send type can be sent to a different thread, a data race and memory corruption can occur...
Memory corruption
An issue was discovered in the va-ts crate before 0.0.4 for Rust. Because Demuxer omits a required T: Send bound, a data race and memory corruption can occur...
Design/Logic Flaw
An issue was discovered in the im crate through 2020-11-09 for Rust. Because TreeFocus does not have bounds on its Send trait or Sync trait, a data race can occur...
Design/Logic Flaw
An issue was discovered in the late-static crate before 0.4.0 for Rust. Because Sync is implemented for LateStatic with T: Send, a data race can occur...
Memory corruption
An issue was discovered in the reffers crate through 2020-12-01 for Rust. ARefss can contain a !Send,!Sync object, leading to a data race and memory corruption...
Design/Logic Flaw
An issue was discovered in the atomic-option crate through 2020-10-31 for Rust. Because AtomicOption implements Sync unconditionally, a data race can occur...
Memory corruption
An issue was discovered in the gfwx crate before 0.3.0 for Rust. Because ImageChunkMut does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur...
Design/Logic Flaw
An issue was discovered in the buttplug crate before 1.0.4 for Rust. ButtplugFutureStateShared does not properly consider !Send|!Sync objects, leading to a data race...
Memory corruption
An issue was discovered in the rusb crate before 0.7.0 for Rust. Because of a lack of Send and Sync bounds, a data race and memory corruption can occur...
golang: data race in certain net/http servers including ReverseProxy can lead to DoS
A flaw was found Go's net/http package. Servers using ReverseProxy from net/http in the Go standard library are vulnerable to a data race that results in a denial of service. The highest threat from this vulnerability is to system availability...
openSUSE Security Update : blosc (openSUSE-2020-2337)
This update for blosc fixes the following issues : Update to version 1.20.1 boo1179914 CVE-2020-29367 : - More saftey checks have been implemented so that potential flaws discovered by new fuzzers in OSS-Fuzzer are fixed now - BloscLZ updated to 2.3.0. Expect better compression ratios for faster...
CVE-2020-36203
An issue was discovered in the reffers crate through 2020-12-01 for Rust. ARefss can contain a !Send,!Sync object, leading to a data race and memory corruption...
CVE-2020-36203
The CVE-2020-36203 issue concerns the reffers crate for Rust, where ARefss can contain a !Send and/or !Sync object, enabling a data race and memory corruption. The root cause is unsafely allowing Send/Sync traits to be assumed for ARefss, permitting insertion of non-Send/Sync objects via ARefss::...
CVE-2020-36204
In the provided documents, CVE-2020-36204 concerns the Rust im crate, where TreeFocus lacks Bounds on Send/Sync, enabling a data race. The issue is described across multiple sources (NVD entry, Red Hat/SUSE advisories, CNVD, GHSA, and RustSec advisory). Affected component: im crate up to 2020-11-...