Advisory

GHSA-7cqx-92hp-x6wh

Also known as: BIT-tensorflow-2021-29576, CVE-2021-29576, PYSEC-2021-213, PYSEC-2021-504, PYSEC-2021-702

Summary

Heap buffer overflow in MaxPool3DGradGrad

Details

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

import tensorflow as tf

values = [0.01] * 11
orig_input = tf.constant(values, shape=[11, 1, 1, 1, 1], dtype=tf.float32)
orig_output = tf.constant([0.01], shape=[1, 1, 1, 1, 1], dtype=tf.float32)
grad = tf.constant([0.01], shape=[1, 1, 1, 1, 1], dtype=tf.float32)
ksize = [1, 1, 1, 1, 1]
strides = [1, 1, 1, 1, 1]
padding = "SAME"

tf.raw_ops.MaxPool3DGradGrad(
    orig_input=orig_input, orig_output=orig_output, grad=grad, ksize=ksize,
    strides=strides, padding=padding)

The implementation does not check that the initialization of Pool3dParameters completes successfully:

Pool3dParameters params{context,  ksize_,       stride_,
                        padding_, data_format_, tensor_in.shape()};

Since the constructor uses OP_REQUIRES to validate conditions, the first assertion that fails interrupts the initialization of params, making it contain invalid data. In turn, this might cause a heap buffer overflow, depending on default initialized values.

Patches
We have patched the issue in GitHub commit 63c6a29d0f2d692b247f7bf81f8732d6442fad09.

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2021-05-21 14:26 UTC
Modified
2026-07-08 06:28 UTC

Affected packages and fixes

12 affected packages; all PyPI · All systems
PackageAffectedFix
tensorflowEarlier versionspip install --upgrade tensorflow==2.1.4
tensorflowintroduced 2.2.0, fixed 2.2.3pip install --upgrade tensorflow==2.2.3
tensorflowintroduced 2.3.0, fixed 2.3.3pip install --upgrade tensorflow==2.3.3
tensorflowintroduced 2.4.0, fixed 2.4.2pip install --upgrade tensorflow==2.4.2
tensorflow-cpuEarlier versionspip install --upgrade tensorflow-cpu==2.1.4
tensorflow-cpuintroduced 2.2.0, fixed 2.2.3pip install --upgrade tensorflow-cpu==2.2.3
tensorflow-cpuintroduced 2.3.0, fixed 2.3.3pip install --upgrade tensorflow-cpu==2.3.3
tensorflow-cpuintroduced 2.4.0, fixed 2.4.2pip install --upgrade tensorflow-cpu==2.4.2
tensorflow-gpuEarlier versionspip install --upgrade tensorflow-gpu==2.1.4
tensorflow-gpuintroduced 2.2.0, fixed 2.2.3pip install --upgrade tensorflow-gpu==2.2.3
tensorflow-gpuintroduced 2.3.0, fixed 2.3.3pip install --upgrade tensorflow-gpu==2.3.3
tensorflow-gpuintroduced 2.4.0, fixed 2.4.2pip install --upgrade tensorflow-gpu==2.4.2

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences