CVE-2021-29576 Heap buffer overflow in `MaxPool3DGradGrad`

Low 2.5 Published Updated

A heap buffer overflow in TensorFlow's MaxPool3DGradGrad operation allows attackers to cause denial of service or execute arbitrary code.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2021-29576?

CVE-2021-29576 is a low-severity memory corruption vulnerability in Google Tensorflow, published on 14 May 2021. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.MaxPool3DGradGrad` is vulnerable to a heap buffer overflow. The implementation(https://github.com/tensorflow/tensorflow/blob/596c05a159b6fbb9e39ca10b3f7753b7244fa1e9/tensorflow/core/kernels/pooling_ops_3d.cc#L694-L696) does not check that the initialization of `Pool3dParameters` completes successfully. Since the constructor(https://github.com/tensorflow/tensorflow/blob/596c05a159b6fbb9e39ca10b3f7753b7244fa1e9/tensorflow/core/kernels/pooling_ops_3d.cc#L48-L88) 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. 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.

Weakness: CWE-787, CWE-119

Which versions are affected by CVE-2021-29576?

28 open source packages ship an affected version, including tensorflow, tensorflow-cpu and tensorflow-gpu. It affects 1 product.

PackageAffectedFixed in
tensorflow BitnamiAll versions2.1.4, 2.2.3, 2.3.3, 2.4.2
tensorflow PyPIAll versions2.1.4, 2.2.3, 2.3.3, 2.4.2
tensorflow PyPIAll versions2.1.4
tensorflow PyPIAll versions2.1.4
tensorflow PyPIFrom 2.2.02.2.3
tensorflow PyPIFrom 2.2.02.2.3
22 more packages
tensorflow PyPIFrom 2.3.02.3.3
tensorflow PyPIFrom 2.3.02.3.3
tensorflow PyPIFrom 2.4.02.4.2
tensorflow PyPIFrom 2.4.02.4.2
tensorflow-cpu PyPIAll versions2.1.4, 2.2.3, 2.3.3, 2.4.2
tensorflow-cpu PyPIAll versions2.1.4
tensorflow-cpu PyPIAll versions2.1.4
tensorflow-cpu PyPIFrom 2.2.02.2.3
tensorflow-cpu PyPIFrom 2.2.02.2.3
tensorflow-cpu PyPIFrom 2.3.02.3.3
tensorflow-cpu PyPIFrom 2.3.02.3.3
tensorflow-cpu PyPIFrom 2.4.02.4.2
tensorflow-cpu PyPIFrom 2.4.02.4.2
tensorflow-gpu PyPIAll versions2.1.4, 2.2.3, 2.3.3, 2.4.2
tensorflow-gpu PyPIAll versions2.1.4
tensorflow-gpu PyPIAll versions2.1.4
tensorflow-gpu PyPIFrom 2.2.02.2.3
tensorflow-gpu PyPIFrom 2.2.02.2.3
tensorflow-gpu PyPIFrom 2.3.02.3.3
tensorflow-gpu PyPIFrom 2.3.02.3.3
tensorflow-gpu PyPIFrom 2.4.02.4.2
tensorflow-gpu PyPIFrom 2.4.02.4.2

Products include Google Tensorflow.

How do I fix CVE-2021-29576?

Upgrade tensorflow to a fixed version for your release line: 2.1.4, 2.2.3, 2.3.3 or 2.4.2.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2021-29576 being exploited?

There is no known exploitation of CVE-2021-29576 in the wild and no public exploit code.

All Google Tensorflow vulnerabilities

Sources

Also known as BIT-tensorflow-2021-29576, GHSA-7cqx-92hp-x6wh, PYSEC-2021-213, PYSEC-2021-504, PYSEC-2021-702.

Is CVE-2021-29576 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free