CVE-2020-15211 Out of bounds access in tensorflow-lite

In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indice...

CVE-2020-15211

CVE-2020-15211 : In TensorFlow Lite (before 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1), a negative -1 tensor index used for optional inputs can be treated as a valid index during validation, allowing out-of-bounds reads/writes in some operators. The root cause is the double indexing scheme for tensors i...

CVE-2020-15211

In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indice...

CVE-2020-15191

CVE-2020-15191 is a TensorFlow vulnerability affecting dlpack.to_dlpack. In TF versions prior to 2.2.1 and 2.3.1, passing an invalid argument to to_dlpack allows the code to bind references to null pointers due to improper status handling, leading to undefined behavior when compiled with -fsaniti...

CVE-2020-15191 Undefined behavior in Tensorflow

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, code...

CVE-2020-15192

CVE-2020-15192 affects TensorFlow and is a memory leak in the dlpack.to_dlpack path when a list of strings is passed. Root cause: the status argument used during validation failures isn’t checked, allowing a potentially failing status to be ignored and leading to memory leakage. Affected: TensorF...

CVE-2020-15192

In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes a list of strings to dlpack.todlpack there is a memory leak following an expected validation failure. The issue occurs because the status argument during validation failures is not properly checked. Since each of the above methods ca...

CVE-2020-15192 Memory leak in Tensorflow

In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes a list of strings to dlpack.todlpack there is a memory leak following an expected validation failure. The issue occurs because the status argument during validation failures is not properly checked. Since each of the above methods ca...

CVE-2020-15193 Memory corruption in Tensorflow

In Tensorflow before versions 2.2.1 and 2.3.1, the implementation of dlpack.todlpack can be made to use uninitialized memory resulting in further memory corruption. This is because the pybind11 glue code assumes that the argument is a tensor. However, there is nothing stopping users from passing ...

CVE-2020-15193

CVE-2020-15193 in TensorFlow arises from dlpack.to_dlpack handling where a non-tensor Python object can lead to uninitialized memory and memory corruption due to an improper reinterpret_cast in pybind11 glue code. The issue is fixed in commit 22e07fb204386768e5bcbea563641ea11f96ceb8 and released ...

CVE-2020-15193

In Tensorflow before versions 2.2.1 and 2.3.1, the implementation of dlpack.todlpack can be made to use uninitialized memory resulting in further memory corruption. This is because the pybind11 glue code assumes that the argument is a tensor. However, there is nothing stopping users from passing ...

CVE-2020-15194

In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the SparseFillEmptyRowsGrad implementation has incomplete validation of the shapes of its arguments. Although reverseindexmapt and gradvaluest are accessed in a similar pattern, only reverseindexmapt is validated to be of proper...

CVE-2020-15194 Denial of Service in Tensorflow

In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the SparseFillEmptyRowsGrad implementation has incomplete validation of the shapes of its arguments. Although reverseindexmapt and gradvaluest are accessed in a similar pattern, only reverseindexmapt is validated to be of proper...

CVE-2020-15194

CVE-2020-15194 (TensorFlow) affects TensorFlow before 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. The SparseFillEmptyRowsGrad implementation has incomplete validation of argument shapes; while reverse_index_map_t is validated, grad_values_t is not, enabling an attacker to pass a bad grad_values_t and ...

CVE-2020-15195

TensorFlow vulnerability CVE-2020-15195: SparseFillEmptyRowsGrad uses a double indexing pattern where reverse_index_map(i) can reference grad_values out of bounds, causing a heap-based buffer overflow. Affected releases include 1.15.4, 2.0.3, 2.1.2, 2.2.1, and 2.3.1. A fix was committed (390611e0...

CVE-2020-15195 Heap buffer overflow in Tensorflow

In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the implementation of SparseFillEmptyRowsGrad uses a double indexing pattern. It is possible for reverseindexmapi to be an index outside of bounds of gradvalues, thus resulting in a heap buffer overflow. The issue is patched in...

CVE-2020-15195

In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the implementation of SparseFillEmptyRowsGrad uses a double indexing pattern. It is possible for reverseindexmapi to be an index outside of bounds of gradvalues, thus resulting in a heap buffer overflow. The issue is patched in...

CVE-2020-15196 Heap buffer overflow in Tensorflow

In Tensorflow version 2.3.0, the SparseCountSparseOutput and RaggedCountSparseOutput implementations don't validate that the weights tensor has the same shape as the data. The check exists for DenseCountSparseOutput, where both tensors are fully specified. In the sparse and ragged count weights a...

CVE-2020-15196

CVE-2020-15196 affects TensorFlow 2.3.0: SparseCountSparseOutput and RaggedCountSparseOutput do not validate that the weights tensor has the same shape as the data, allowing reads beyond the weights buffer when fewer weights are provided. This heap-based overflow is mitigated in TensorFlow 2.3.1 ...