Heap buffer overflow in `RaggedTensorToTensor`
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
2.1.42.2.32.3.32.4.22.2.0rc02.3.0rc02.3.42.4.3| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a heap buffer overflow in `tf.raw_ops.RaggedTensorToTensor`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/d94227d43aa125ad8b54115c03cece54f6a1977b/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L219-L222) uses the same index to access two arrays in parallel. Since the user controls the shape of the input arguments, an attacker could trigger a heap OOB access when `parent_output_index` is shorter than `row_split`. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
From the CVE record · GitHub_M
`tf.raw_ops.RaggedTensorToTensor` can access memory outside a heap buffer when `parent_output_index` is shorter than `row_split`. An attacker who controls the input shapes can trigger this condition; the input does not specify whether network access, authentication, or user interaction is required.
Engineers using affected versions of the PyPI `tensorflow`, `tensorflow-cpu`, or `tensorflow-gpu` packages should check their installations.