Heap buffer overflow in Tensorflow
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
2.3.1| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
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 `reverse_index_map(i)` to be an index outside of bounds of `grad_values`, thus resulting in a heap buffer overflow. The issue is patched in commit 390611e0d45c5793c7066110af37c8514e6a6c54, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
From the CVE record · GitHub_M
TensorFlow’s SparseFillEmptyRowsGrad implementation can access grad_values out of bounds when reverse_index_map(i) produces an invalid index, causing a heap buffer overflow. The input does not specify how an attacker could trigger this condition or whether network access, authentication, or user interaction is required.
Users of the PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu packages should check installations below 1.15.4, or in the 2.0.x, 2.1.x, 2.2.x, or 2.3.x lines before 2.0.3, 2.1.2, 2.2.1, or 2.3.1, respectively.