Null pointer dereference in `RaggedTensorToTensor` 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 |
|
|
TensorFlow is an end-to-end open source platform for machine learning. Sending invalid argument for `row_partition_types` of `tf.raw_ops.RaggedTensorToTensor` API results in a null pointer dereference and undefined behavior. The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L328) accesses the first element of a user supplied list of values without validating that the provided list is not empty. We have patched the issue in GitHub commit 301ae88b331d37a2a16159b65b255f4f9eb39314. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
From the CVE record · GitHub_M
TensorFlow's `tf.raw_ops.RaggedTensorToTensor` does not check whether a supplied `row_partition_types` list is empty before accessing its first element. Someone who can supply an empty list to this API can trigger a null pointer dereference and undefined behavior. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Teams using PyPI `tensorflow`, `tensorflow-cpu`, or `tensorflow-gpu` versions before 2.3.4, from 2.4.0 to before 2.4.3, or from 2.5.0 to before 2.5.1 should check their installations.