Reference binding to nullptr in `MatrixSetDiagV*` ops in TensorFlow

Summary

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 all operations of type `tf.raw_ops.MatrixSetDiagV*`. The implementation has incomplete validation that the value of `k` is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong. We have patched the issue in GitHub commit ff8894044dfae5568ecbf2ed514c1a37dc394f1b. 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:50 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

• tensorflow-gpuPyPI

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

• tensorflowPyPI

  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