Heap buffer overflow due to incorrect hash function in TensorFlow
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
≥ 2.8.0 · < 2.8.1
|
TensorFlow is an open source platform for machine learning. In version 2.8.0, the `TensorKey` hash function used total estimated `AllocatedBytes()`, which (a) is an estimate per tensor, and (b) is a very poor hash function for constants (e.g. `int32_t`). It also tried to access individual tensor bytes through `tensor.data()` of size `AllocatedBytes()`. This led to ASAN failures because the `AllocatedBytes()` is an estimate of total bytes allocated by a tensor, including any pointed-to constructs (e.g. strings), and does not refer to contiguous bytes in the `.data()` buffer. The discoverers could not use this byte vector anyway because types such as `tstring` include pointers, whereas they needed to hash the string values themselves. This issue is patched in Tensorflow versions 2.9.0 and 2.8.1.
From the CVE record · GitHub_M
In TensorFlow 2.8.0, the TensorKey hash function can read beyond a tensor’s data buffer because it uses an estimated allocation size as the buffer length. This has caused ASAN failures; the input does not establish how an attacker could trigger it or whether network access, authentication, or user interaction is required.
Engineers running TensorFlow 2.8.0, including the PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu packages, should check their installations.