CVE-2022-21725: Division by zero in Tensorflow

Published Feb 3, 2022
·
Updated

Impact The estimator for the cost of some convolution operations can be made to execute a division by 0:

python import tensorflow as tf

@tf.function def test(): y=tf.rawops.AvgPoolGrad( originputshape=[1,1,1,1], grad=[[[[1.0],[1.0],[1.0]]],[[[2.0],[2.0],[2.0]]],[[[3.0],[3.0],[3.0]]]], ksize=[1,1,1,1], strides=[1,1,1,0], padding='VALID', dataformat='NCHW') return y

test()

The function fails to check that the stride argument is stricly positive:

cc int64t GetOutputSize(const int64t input, const int64t filter, const int64t stride, const Padding& padding) { // Logic for calculating output shape is from GetWindowedOutputSizeVerbose() // function in thirdparty/tensorflow/core/framework/commonshapefns.cc. if (padding == Padding::VALID) { return (input - filter + stride) / stride; } else { // SAME. return (input + stride - 1) / stride; } }

Hence, the fix is to add a check for the stride argument to ensure it is valid.

Patches We have patched the issue in GitHub commit 3218043d6d3a019756607643cf65574fbfef5d7a.

The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, 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 Yu Tian of Qihoo 360 AIVul Team.

Other sources

Tensorflow is an Open Source Machine Learning Framework. The estimator for the cost of some convolution operations can be made to execute a division by 0. The function fails to check that the stride argument is strictly positive. Hence, the fix is to add a check for the stride argument to ensure it is valid. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.

Affected Software

12 affected componentsFixes available
pip/tensorflow-gpu=2.7.0
2.7.1
pip/tensorflow-gpu>=2.6.0<2.6.3
2.6.3
pip/tensorflow-gpu<2.5.3
2.5.3
pip/tensorflow-cpu=2.7.0
2.7.1
pip/tensorflow-cpu>=2.6.0<2.6.3
2.6.3
pip/tensorflow-cpu<2.5.3
2.5.3
pip/tensorflow=2.7.0
2.7.1
pip/tensorflow>=2.6.0<2.6.3
2.6.3
pip/tensorflow<2.5.3
2.5.3
Google TensorFlow<=2.5.2
Google TensorFlow>=2.6.0<=2.6.2
Google TensorFlow=2.7.0

Event History

Feb 3, 2022
CVE Published
via MITRE·12:21 PM
Data Sourced
via MITRE·12:21 PM
DescriptionSeverity
Feb 10, 2022
Advisory Published
via GitHub·12:15 AM

Frequently Asked Questions

1

What is the severity of CVE-2022-21725?

CVE-2022-21725 has a moderate severity rating due to the potential for denial of service caused by a division by zero error.

2

How do I fix CVE-2022-21725?

To fix CVE-2022-21725, upgrade TensorFlow to version 2.5.3, 2.6.3, or 2.7.1 or later.

3

What impact does CVE-2022-21725 have on TensorFlow operations?

CVE-2022-21725 can disrupt some convolution operations, potentially causing application failures.

4

Is CVE-2022-21725 exploitable remotely?

No, CVE-2022-21725 is not considered to be easily exploitable remotely as it primarily affects local execution of TensorFlow.

5

When was CVE-2022-21725 published?

CVE-2022-21725 was published in January 2022.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203