Heap OOB in `ResourceScatterUpdate` in TensorFlow

Summary

TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a read from outside of bounds of heap allocated data by sending invalid arguments to `tf.raw_ops.ResourceScatterUpdate`. The implementation has an incomplete validation of the relationship between the shapes of `indices` and `updates`: instead of checking that the shape of `indices` is a prefix of the shape of `updates` (so that broadcasting can happen), code only checks that the number of elements in these two tensors are in a divisibility relationship. We have patched the issue in GitHub commit 01cff3f986259d661103412a20745928c727326f. 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.

Timeline

1. Aug 12, 2021, 8:25 PM UTCCVE published
2. Aug 4, 2024, 1:23 AM UTCRecord last updated

Affected versions

• tensorflow tensorflow

  From 2.5.0 · fixed in 2.5.1; From 2.4.0 · fixed in 2.4.3; fixed in 2.3.4

• tensorflowPyPI

  fixed in 2.3.4

• tensorflowPyPI

  From 2.4.0 · fixed in 2.4.3

• tensorflowPyPI

  From 2.5.0 · fixed in 2.5.1

• tensorflow-cpuPyPI

  fixed in 2.3.4

• tensorflow-cpuPyPI

  From 2.4.0 · fixed in 2.4.3

• tensorflow-cpuPyPI

  From 2.5.0 · fixed in 2.5.1

• tensorflow-gpuPyPI

  fixed in 2.3.4

• tensorflow-gpuPyPI

  From 2.4.0 · fixed in 2.4.3

• tensorflow-gpuPyPI

  From 2.5.0 · fixed in 2.5.1

• tensorflowPyPI

  From 2.3.0 · fixed in 2.3.4; From 2.4.0 · fixed in 2.4.3

• tensorflow-gpuPyPI

  From 2.3.0 · fixed in 2.3.4; From 2.4.0 · fixed in 2.4.3

• tensorflow-cpuPyPI

  From 2.3.0 · fixed in 2.3.4; From 2.4.0 · fixed in 2.4.3

References 2