CVE-2020-35904: Undefined Security Weakness

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-35919: Undefined Security Weakness

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: Undefined Security Weakness

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-35922: Undefined Security Weakness

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-28925: Undefined Security Weakness

Bolt before 3.7.2 does not restrict filter options in a Request in the Twig context, and is therefore inconsistent with the "How to Harden Your PHP for Better Security" guidance...

pygments:pygments_fuzzer: Uncaught exception in get_tokens_unprocessed

Project: https://github.com/pygments/pygments.git Detailed Report: https://oss-fuzz.com/testcase?key=4836579327737856 Project: pygments Fuzzing Engine: libFuzzer Fuzz Target: pygmentsfuzzer Job Type: libfuzzerubsanpygments Platform Id: linux Crash Type: Uncaught exception Crash Address: Crash...

RUSTSEC-2020-0155 `Read` on uninitialized buffer in `fill_buf()` and `read_up_to()`

Affected versions of this crate passes an uninitialized buffer to a user-provided Read implementation. Arbitrary Read implementations can read from the uninitialized buffer memory exposure and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory...

`Read` on uninitialized buffer in `fill_buf()` and `read_up_to()`

Affected versions of this crate passes an uninitialized buffer to a user-provided Read implementation. Arbitrary Read implementations can read from the uninitialized buffer memory exposure and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory...

Queues allow non-Send types to be sent to other threads, allowing data races

Affected versions of this crate unconditionally implemented Send for types used in queue implementations InnerSend, InnerRecv, FutInnerSend, FutInnerRecv. This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior...

RUSTSEC-2020-0143 Queues allow non-Send types to be sent to other threads, allowing data races

Affected versions of this crate unconditionally implemented Send for types used in queue implementations InnerSend, InnerRecv, FutInnerSend, FutInnerRecv. This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior...

PT-2020-17645

Name of the Vulnerable Software and Affected Versions multiqueue crate through 2020-12-25 Description An issue in the multiqueue crate allows unconditional implementations of Send for types used in queue implementations, such as InnerSend, InnerRecv, FutInnerSend, and FutInnerRecv. This can lead ...

pcapplusplus:FuzzTarget: Bad-cast to pcpp::Layer from invalid vptr in pcpp::IDnsResource::getRawData

Detailed Report: https://oss-fuzz.com/testcase?key=5731167462621184 Project: pcapplusplus Fuzzing Engine: libFuzzer Fuzz Target: FuzzTarget Job Type: libfuzzerubsanpcapplusplus Platform Id: linux Crash Type: Bad-cast Crash Address: 0x0000031c4200 Crash State: Bad-cast to pcpp::Layer from invalid...

Undefined Behavior

encoding/xml in github.com/golang/go is vulnerable to undefined behavior. The vulnerability is possible because it does not correctly preserve the semantics of directives during tokenization round-trips...

`Demuxer` can carry non-Send types across thread boundaries

In the affected versions of this crate, Demuxer unconditionally implemented Send with no trait bounds on T. This allows sending a non-Send type T across thread boundaries, which can cause undefined behavior like unlocking a mutex from a thread that didn't lock the mutex, or memory corruption from...

RUSTSEC-2020-0114 `Demuxer` can carry non-Send types across thread boundaries

In the affected versions of this crate, Demuxer unconditionally implemented Send with no trait bounds on T. This allows sending a non-Send type T across thread boundaries, which can cause undefined behavior like unlocking a mutex from a thread that didn't lock the mutex, or memory corruption from...

PT-2020-17579

Name of the Vulnerable Software and Affected Versions conquer-once versions prior to 0.3.2 Description An issue in the conquer-once crate allows non-Send but Sync types, such as MutexGuard, to be sent across threads, leading to undefined behavior and memory corruption in concurrent programs. This...

PT-2020-17593

Name of the Vulnerable Software and Affected Versions va-ts crate versions prior to 0.0.4 Description The issue arises from the Demuxer implementation in the va-ts crate, which lacks a required T: Send bound. This omission allows sending a non-Send type T across thread boundaries, potentially...

CVE-2020-5808: Undefined Security Weakness

In certain scenarios in Tenable.sc prior to 5.17.0, a scanner could potentially be used outside the user's defined scan zone without a particular zone being specified within the Automatic Distribution configuration...

RUSTSEC-2020-0108 Soundness issue: Input<R> can be misused to create data race to an object

Input implements Send without requiring R: Send. Affected versions of this crate allows users to send non-Send types to other threads, which can lead to undefined behavior such as data race and memory corruption. The flaw was corrected in version 0.5.1 by adding R: Send bound to the Send impl of...

Soundness issue: Input<R> can be misused to create data race to an object

Input implements Send without requiring R: Send. Affected versions of this crate allows users to send non-Send types to other threads, which can lead to undefined behavior such as data race and memory corruption. The flaw was corrected in version 0.5.1 by adding R: Send bound to the Send impl of...