PT-2020-17642

Name of the Vulnerable Software and Affected Versions model crate through 2020-11-10 Description An issue was discovered in the Shared data structure, which implements the Send and Sync traits without regard for the inner type. This allows safe Rust code to trigger a data race, which is undefined...

PT-2020-17620

Name of the Vulnerable Software and Affected Versions libsbc crate versions prior to 0.1.5 Description The issue allows Decoder to contain R: !Send and carry it to another thread, resulting in undefined behavior such as memory corruption from data race on R, or dropping R = MutexGuard from a thre...

simdjson:fuzz_ondemand: Crash in jsoncharutils.h

Project: https://github.com/simdjson/simdjson.git https://github.com/lemire/simdjson.git Detailed Report: https://oss-fuzz.com/testcase?key=6259259773550592 Project: simdjson Fuzzing Engine: libFuzzer Fuzz Target: fuzzondemand Job Type: libfuzzerubsansimdjson Platform Id: linux Crash Type: UNKNOW...

RUSTSEC-2020-0113 AtomicOption should have Send + Sync bound on its type argument.

In the affected versions of this crate, AtomicOption unconditionally implements Sync. This allows programmers to move non-Sync types across thread boundaries e.g. Rc, Arc, which can lead to data races and undefined behavior. It is also possible to send non-Send types like std::sync::MutexGuard to...

AtomicOption should have Send + Sync bound on its type argument.

In the affected versions of this crate, AtomicOption unconditionally implements Sync. This allows programmers to move non-Sync types across thread boundaries e.g. Rc, Arc, which can lead to data races and undefined behavior. It is also possible to send non-Send types like std::sync::MutexGuard to...

PT-2020-17591

Name of the Vulnerable Software and Affected Versions atomic-option crate through 2020-10-31 Description The issue concerns the atomic-option crate, where AtomicOption unconditionally implements Sync. This allows moving non-Sync types, such as Rc or Arc, across thread boundaries, potentially...

OPENSUSE-SU-2020:1766-1 Security update for tensorflow2

This update for tensorflow2 fixes the following issues: - updated to 2.1.2 with following fixes boo1177022: Fixes an undefined behavior causing a segfault in tf.rawops.Switch CVE-2020-15190 Fixes three vulnerabilities in conversion to DLPack format CVE-2020-15191, CVE-2020-15192, CVE-2020-15193...

Remote Code Execution (RCE)

firefox is vulnerable to remote code execution RCE. The vulnerability exists through an undefined behavior in bounded channel of crossbeam rust crate...

CVE-2020-15266 Undefined behavior in Tensorflow

In Tensorflow before version 2.4.0, when the boxes argument of tf.image.cropandresize has a very large value, the CPU kernel implementation receives it as a C++ nan floating point value. Attempting to operate on this is undefined behavior which later produces a segmentation fault. The issue is...

c-blosc2:decompress_fuzzer: Crash with empty stacktrace

Detailed Report: https://oss-fuzz.com/testcase?key=4881454368292864 Project: c-blosc2 Fuzzing Engine: libFuzzer Fuzz Target: decompressfuzzer Job Type: libfuzzerubsanc-blosc2 Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x7eff01954260 Crash State: NULL Sanitizer: undefined UBSAN...

Design/Logic Flaw

In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to dlpack.todlpack the expected validations will cause variables to bind to nullptr while setting a status variable to the error condition. However, this status argument is not properly checked. Hence, code...

PYSEC-2020-306

In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to dlpack.todlpack the expected validations will cause variables to bind to nullptr while setting a status variable to the error condition. However, this status argument is not properly checked. Hence, code...

CVE-2020-15191

In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to "dlpack.todlpack" the expected validations will cause variables to bind to "nullptr" while setting a "status" variable to the error condition. However, this "status" argument is not properly checked. Hence, cod...

CVE-2020-15190

In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the tf.rawops.Switch operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor. Howeve...

CVE-2020-15190

In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the "tf.rawops.Switch" operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor...

GHSA-Q8QJ-FC9Q-CPHR Undefined behavior in Tensorflow

Impact If a user passes an invalid argument to dlpack.todlpack the expected validations will cause variables to bind to nullptr while setting a status variable to the error condition. However, this status argument is not properly checked:...

Undefined behavior in Tensorflow

Impact If a user passes an invalid argument to dlpack.todlpack the expected validations will cause variables to bind to nullptr while setting a status variable to the error condition. However, this status argument is not properly checked:...

CVE-2020-15190: Improper Input Validation

In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the tf.rawops.Switch operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor. Howeve...

PT-2020-14262 · Google +1 · Tensorflow +1

Name of the Vulnerable Software and Affected Versions: Tensorflow versions prior to 2.2.1 Tensorflow versions prior to 2.3.1 Description: The issue arises when a user passes an invalid argument to dlpack.to dlpack, causing variables to bind to nullptr while setting a status variable to the error...

CVE-2020-15191: Improper Input Validation

In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to dlpack.todlpack the expected validations will cause variables to bind to nullptr while setting a status variable to the error condition. However, this status argument is not properly checked. Hence, code...