Reference binding to nullptr in map operations 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. In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.Map*` and `tf.raw_ops.OrderedMap*` operations. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L222-L248) has a check in place to ensure that `indices` is in ascending order, but does not check that `indices` is not empty. We have patched the issue in GitHub commit 532f5c5a547126c634fefd43bbad1dc6417678ac. 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
Affected TensorFlow versions can bind a reference to a null pointer in `tf.raw_ops.Map*` and `tf.raw_ops.OrderedMap*` operations because they do not check whether `indices` is empty. An attacker who can cause these operations to receive empty `indices` can trigger undefined behavior. The input does not specify network access, authentication requirements, or user interaction.
Teams using affected versions of the PyPI packages `tensorflow`, `tensorflow-cpu`, or `tensorflow-gpu`, including versions before 2.3.4 and versions 2.4.0–2.4.2 or 2.5.0, should check their installations.