Heap buffer overflow in Tensorflow
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
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.
From the CVE record · GitHub_M
TensorFlow before 2.3.1 does not check that the indices and values inputs to SparseCountSparseOutput have matching shapes. A malformed sparse tensor can cause out-of-bounds access to heap-allocated buffers. The input does not specify network or local access, authentication requirements, or user interaction.
Check deployments using affected PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu packages before version 2.3.1.