CVE-2021-29517 Division by zero in `Conv3D`
A malicious user can trigger a division by zero or assertion failure in Conv3D, causing a program crash and denial of service.
- 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-29517?
CVE-2021-29517 is a low-severity denial of service 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. A malicious user could trigger a division by 0 in `Conv3D` implementation. The implementation(https://github.com/tensorflow/tensorflow/blob/42033603003965bffac51ae171b51801565e002d/tensorflow/core/kernels/conv_ops_3d.cc#L143-L145) does a modulo operation based on user controlled input. Thus, when `filter` has a 0 as the fifth element, this results in a division by 0. Additionally, if the shape of the two tensors is not valid, an Eigen assertion can be triggered, resulting in a program crash. 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-369
Which versions are affected by CVE-2021-29517?
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-29517?
Upgrade tensorflow to a fixed version for your release line: 2.1.4, 2.2.3, 2.3.3 or 2.4.2.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2021-29517 being exploited?
There is no known exploitation of CVE-2021-29517 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-29517, GHSA-772p-x54p-hjrv, PYSEC-2021-154, PYSEC-2021-445, PYSEC-2021-643.