Filtered by vendor Google
Subscriptions
Filtered by product Tensorflow
Subscriptions
Total
429 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2020-15190 | 2 Google, Opensuse | 2 Tensorflow, Leap | 2024-11-21 | 5.3 Medium |
| In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `tf.raw_ops.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. However, the eager runtime traverses all tensors in the output. Since only one of the tensors is defined, the other one is `nullptr`, hence we are binding a reference to `nullptr`. This is undefined behavior and reported as an error if compiling with `-fsanitize=null`. In this case, this results in a segmentation fault The issue is patched in commit da8558533d925694483d2c136a9220d6d49d843c, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. | ||||
| CVE-2019-9635 | 1 Google | 1 Tensorflow | 2024-11-21 | N/A |
| NULL pointer dereference in Google TensorFlow before 1.12.2 could cause a denial of service via an invalid GIF file. | ||||
| CVE-2019-16778 | 1 Google | 1 Tensorflow | 2024-11-21 | 2.6 Low |
| In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be produced when the Index template argument is int32. In this case data_size and num_segments fields are truncated from int64 to int32 and can produce negative numbers, resulting in accessing out of bounds heap memory. This is unlikely to be exploitable and was detected and fixed internally in TensorFlow 1.15 and 2.0. | ||||
| CVE-2018-8825 | 1 Google | 1 Tensorflow | 2024-11-21 | N/A |
| Google TensorFlow 1.7 and below is affected by: Buffer Overflow. The impact is: execute arbitrary code (local). | ||||
| CVE-2018-7577 | 1 Google | 2 Snappy, Tensorflow | 2024-11-21 | N/A |
| Memcpy parameter overlap in Google Snappy library 1.1.4, as used in Google TensorFlow before 1.7.1, could result in a crash or read from other parts of process memory. | ||||
| CVE-2018-7576 | 1 Google | 1 Tensorflow | 2024-11-21 | N/A |
| Google TensorFlow 1.6.x and earlier is affected by: Null Pointer Dereference. The type of exploitation is: context-dependent. | ||||
| CVE-2018-7575 | 1 Google | 1 Tensorflow | 2024-11-21 | N/A |
| Google TensorFlow 1.7.x and earlier is affected by a Buffer Overflow vulnerability. The type of exploitation is context-dependent. | ||||
| CVE-2018-21233 | 1 Google | 1 Tensorflow | 2024-11-21 | 6.5 Medium |
| TensorFlow before 1.7.0 has an integer overflow that causes an out-of-bounds read, possibly causing disclosure of the contents of process memory. This occurs in the DecodeBmp feature of the BMP decoder in core/kernels/decode_bmp_op.cc. | ||||
| CVE-2018-10055 | 1 Google | 1 Tensorflow | 2024-11-21 | N/A |
| Invalid memory access and/or a heap buffer overflow in the TensorFlow XLA compiler in Google TensorFlow before 1.7.1 could cause a crash or read from other parts of process memory via a crafted configuration file. | ||||