CVE-2020-15198 — Google Tensorflow vulnerability

Vendor	Product	Version range	Fixed in
debian	tensorflow	—	—
google	tensorflow	>= 2.3.0 < 2.3.1	2.3.1
intel	optimization_for_tensorflow	>= 0 < 3cbb917b4714766030b28eba9fb41bb97ce9ee02	3cbb917b4714766030b28eba9fb41bb97ce9ee02
intel	optimization_for_tensorflow	>= 0 < 2.3.1	2.3.1
intel	optimization_for_tensorflow	>= 2.3.0 < 2.3.1	2.3.1
tensorflow	tensorflow	—	—

GHSA

Heap buffer overflow in Tensorflow

ghsa·2020-09-25

CVE-2020-15198 [MEDIUM] CWE-119 Heap buffer overflow in Tensorflow Heap buffer overflow in Tensorflow ### Impact The `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has the same shape as the `values` one. The values in these tensors are always accessed in parallel: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L193-L195 Thus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers. ### Patches We have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release. We recommend users to upgrade to TensorFlow 2.3.1. ### For more information Please consult [our security guide](https://github

OSV

Heap buffer overflow in Tensorflow

osv·2020-09-25

CVE-2020-15198 [MEDIUM] Heap buffer overflow in Tensorflow Heap buffer overflow in Tensorflow ### Impact The `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has the same shape as the `values` one. The values in these tensors are always accessed in parallel: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L193-L195 Thus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers. ### Patches We have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release. We recommend users to upgrade to TensorFlow 2.3.1. ### For more information Please consult [our security guide](https://github

OSV

CVE-2020-15198: In Tensorflow before version 2

osv·2020-09-25

CVE-2020-15198 CVE-2020-15198: In Tensorflow before version 2 In Tensorflow before version 2.3.1, the `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has the same shape as the `values` one. The values in these tensors are always accessed in parallel. Thus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1.

Debian

CVE-2020-15198: tensorflow - In Tensorflow before version 2.3.1, the `SparseCountSparseOutput` implementation...

vendor_debian·2020·CVSS 5.4

CVE-2020-15198 [MEDIUM] CVE-2020-15198: tensorflow - In Tensorflow before version 2.3.1, the `SparseCountSparseOutput` implementation... In Tensorflow before version 2.3.1, the `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has the same shape as the `values` one. The values in these tensors are always accessed in parallel. Thus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1. Scope: local forky: resolved sid: resolved

CVE-2020-15198: In Tensorflow before version 2.3.1, the `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In…

Affected