CVE-2021-29574 Undefined behavior in `MaxPool3DGradGrad`
An attacker can cause a denial of service by supplying empty tensors to MaxPool3DGradGrad, triggering a null pointer dereference in TensorFlow.
- 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-29574?
CVE-2021-29574 is a low-severity 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` 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.
Weakness: CWE-476
Which versions are affected by CVE-2021-29574?
28 open source packages ship an affected version, including tensorflow, tensorflow-cpu and tensorflow-gpu. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
tensorflow Bitnami | All versions | 2.1.4, 2.2.3, 2.3.3, 2.4.2 |
tensorflow PyPI | All versions | 2.1.4, 2.2.3, 2.3.3, 2.4.2 |
tensorflow PyPI | All versions | 2.1.4 |
tensorflow PyPI | All versions | 2.1.4 |
tensorflow PyPI | From 2.2.0 | 2.2.3 |
tensorflow PyPI | From 2.2.0 | 2.2.3 |
22 more packages
tensorflow PyPI | From 2.3.0 | 2.3.3 |
tensorflow PyPI | From 2.3.0 | 2.3.3 |
tensorflow PyPI | From 2.4.0 | 2.4.2 |
tensorflow PyPI | From 2.4.0 | 2.4.2 |
tensorflow-cpu PyPI | All versions | 2.1.4, 2.2.3, 2.3.3, 2.4.2 |
tensorflow-cpu PyPI | All versions | 2.1.4 |
tensorflow-cpu PyPI | All versions | 2.1.4 |
tensorflow-cpu PyPI | From 2.2.0 | 2.2.3 |
tensorflow-cpu PyPI | From 2.2.0 | 2.2.3 |
tensorflow-cpu PyPI | From 2.3.0 | 2.3.3 |
tensorflow-cpu PyPI | From 2.3.0 | 2.3.3 |
tensorflow-cpu PyPI | From 2.4.0 | 2.4.2 |
tensorflow-cpu PyPI | From 2.4.0 | 2.4.2 |
tensorflow-gpu PyPI | All versions | 2.1.4, 2.2.3, 2.3.3, 2.4.2 |
tensorflow-gpu PyPI | All versions | 2.1.4 |
tensorflow-gpu PyPI | All versions | 2.1.4 |
tensorflow-gpu PyPI | From 2.2.0 | 2.2.3 |
tensorflow-gpu PyPI | From 2.2.0 | 2.2.3 |
tensorflow-gpu PyPI | From 2.3.0 | 2.3.3 |
tensorflow-gpu PyPI | From 2.3.0 | 2.3.3 |
tensorflow-gpu PyPI | From 2.4.0 | 2.4.2 |
tensorflow-gpu PyPI | From 2.4.0 | 2.4.2 |
Products include Google Tensorflow.
How do I fix CVE-2021-29574?
Upgrade tensorflow to a fixed version for your release line: 2.1.4, 2.2.3, 2.3.3 or 2.4.2.
Is CVE-2021-29574 being exploited?
There is no known exploitation of CVE-2021-29574 in the wild and no public exploit code.
Other vulnerabilities in Google Tensorflow
- CVE-2023-25668 TensorFlow vulnerable to heap out-of-buffer read in the QuantizeAndDequantize operation
- CVE-2018-7575 Integer Overflow or Wraparound in Google TensorFlow
- CVE-2021-37678 Arbitrary code execution due to YAML deserialization
- CVE-2021-35958 Path traversal in n/a
- CVE-2020-15202 Integer truncation in Shard API usage
Sources
Also known as BIT-tensorflow-2021-29574, GHSA-828x-qc2p-wprq, PYSEC-2021-211, PYSEC-2021-502, PYSEC-2021-700.