CVE-2021-29524: TensorFlow Division by Zero in Conv2DBackpropFilter
Summary
CVE-2021-29524: TensorFlow is an end-to-end open source platform for machine learning. Affects tensorflow across 5 version ranges.
< 2.1.4
>= 2.2.0, < 2.2.3
>= 2.3.0, < 2.3.3
>= 2.4.0, < 2.4.2
< fca9874a9b42a2134f907d2fb46ab774a831404a
Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓
Also tracked for
- tensorflow · Bitnami
- tensorflow-cpu · PyPI
- tensorflow-gpu · PyPI
The same CVE-2021-29524 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
TensorFlow is an end-to-end open source platform for machine learning. It provides a comprehensive ecosystem of tools, libraries, and resources for developing and deploying machine learning models. TensorFlow is widely used in various domains, including research, industry, and academia. It offers functionalities for building neural networks, training models, and performing inference on large datasets. However, a vulnerability has been identified in TensorFlow that can lead to a division by zero in the tf.raw_ops.Conv2DBackpropFilter function.
Vulnerability Detail
The vulnerability arises from a modulus operation in the implementation of tf.raw_ops.Conv2DBackpropFilter, where the divisor is controlled by the caller. An attacker can exploit this by providing a divisor of zero, triggering a division by zero error. This vulnerability can potentially be exploited to cause denial of service (DoS) attacks or to manipulate the behavior of the affected TensorFlow application. The issue has been assigned the identifier CVE-2021-29524.
How To Fix
Latest published version: 2.21.0 as of 22 Oct 2026
pip install --upgrade "tensorflow==2.21.0"
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 2.1.42.1.4pip install --upgrade "tensorflow==2.1.4" -
>= 2.2.0, < 2.2.32.2.3pip install --upgrade "tensorflow==2.2.3" -
>= 2.3.0, < 2.3.32.3.3pip install --upgrade "tensorflow==2.3.3" -
>= 2.4.0, < 2.4.22.4.2pip install --upgrade "tensorflow==2.4.2"
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a temporary workaround, users can validate the divisor before calling the tf.raw_ops.Conv2DBackpropFilter function to ensure it is not zero. This can be done by adding a simple check in the code, as shown in the following Python snippet:
if divisor != 0:
# Call tf.raw_ops.Conv2DBackpropFilter
else:
# Handle the case when divisor is zero
By performing this check, the division by zero error can be avoided.
Conclusion
In conclusion, a division by zero vulnerability has been identified in TensorFlow's tf.raw_ops.Conv2DBackpropFilter function. This vulnerability can be mitigated by updating to the latest available version of TensorFlow or by implementing a temporary workaround to validate the divisor. It is recommended to promptly apply the necessary fixes to ensure the security and stability of TensorFlow applications. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for tensorflow →
FAQ
TensorFlow is an open source platform for machine learning that provides tools and resources for developing and deploying machine learning models.
This vulnerability can be exploited to cause denial of service (DoS) attacks or to manipulate the behavior of the affected TensorFlow application.
The vulnerability affects TensorFlow versions 2.1.4 and above, including TensorFlow 2.2.3, TensorFlow 2.3.3, and TensorFlow 2.4.2.
To fix this vulnerability, update your TensorFlow installation to the latest available version (TensorFlow 2.5.0 or above).
Yes, a temporary workaround is to validate the divisor before calling the vulnerable function to ensure it is not zero.
References
Related vulnerabilities
Recent vulnerabilities recorded for tensorflow.