Undefined behavior in `MaxPool3DGradGrad`

Summary

TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.MaxPool3DGradGrad` exhibits undefined behavior by dereferencing null pointers backing attacker-supplied empty tensors. The implementation(https://github.com/tensorflow/tensorflow/blob/72fe792967e7fd25234342068806707bbc116618/tensorflow/core/kernels/pooling_ops_3d.cc#L679-L703) fails to validate that the 3 tensor inputs are not empty. If any of them is empty, then accessing the elements in the tensor results in dereferencing a null pointer. 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.

Timeline

1. May 14, 2021, 7:16 PM UTCCVE published
2. Aug 3, 2024, 10:11 PM UTCRecord last updated

Affected versions

• tensorflow tensorflow

  fixed in 2.1.4; From 2.2.0 · fixed in 2.2.3; From 2.3.0 · fixed in 2.3.3; From 2.4.0 · fixed in 2.4.2

• tensorflow-cpuPyPI

  fixed in 2.1.4; From 2.2.0 · fixed in 2.2.3; From 2.3.0 · fixed in 2.3.3; From 2.4.0 · fixed in 2.4.2

• tensorflowPyPI

  fixed in 2.1.4; From 2.2.0 · fixed in 2.2.3; From 2.3.0 · fixed in 2.3.3; From 2.4.0 · fixed in 2.4.2

• tensorflow-gpuPyPI

  fixed in 2.1.4; From 2.2.0 · fixed in 2.2.3; From 2.3.0 · fixed in 2.3.3; From 2.4.0 · fixed in 2.4.2

• tensorflowPyPI

  fixed in 2.1.4

• tensorflowPyPI

  From 2.2.0 · fixed in 2.2.3

• tensorflowPyPI

  From 2.3.0 · fixed in 2.3.3

• tensorflowPyPI

  From 2.4.0 · fixed in 2.4.2

• tensorflow-cpuPyPI

  fixed in 2.1.4

• tensorflow-cpuPyPI

  From 2.2.0 · fixed in 2.2.3

• tensorflow-cpuPyPI

  From 2.3.0 · fixed in 2.3.3

• tensorflow-cpuPyPI

  From 2.4.0 · fixed in 2.4.2

• tensorflow-gpuPyPI

  fixed in 2.1.4

• tensorflow-gpuPyPI

  From 2.2.0 · fixed in 2.2.3

• tensorflow-gpuPyPI

  From 2.3.0 · fixed in 2.3.3

• tensorflow-gpuPyPI

  From 2.4.0 · fixed in 2.4.2

References 2