medium
6.5
CWE
190
Advisory Published
Advisory Published
Updated

CVE-2022-21738: Integer overflow leading to crash in Tensorflow

First published: Thu Feb 03 2022(Updated: )

### Impact The [implementation of `SparseCountSparseOutput`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/count_ops.cc#L168-L273) can be made to crash a TensorFlow process by an integer overflow whose result is then used in a memory allocation: ```python import tensorflow as tf import numpy as np tf.raw_ops.SparseCountSparseOutput( indices=[[1,1]], values=[2], dense_shape=[2 ** 31, 2 ** 32], weights=[1], binary_output=True, minlength=-1, maxlength=-1, name=None) ``` ### Patches We have patched the issue in GitHub commit [6f4d3e8139ec724dbbcb40505891c81dd1052c4a](https://github.com/tensorflow/tensorflow/commit/6f4d3e8139ec724dbbcb40505891c81dd1052c4a). 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](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported by Faysal Hossain Shezan from University of Virginia.

Credit: security-advisories@github.com security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
Google TensorFlow<=2.5.2
Google TensorFlow>=2.6.0<=2.6.2
Google TensorFlow=2.7.0
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

Remedy

https://github.com/tensorflow/tensorflow/commit/6f4d3e8139ec724dbbcb40505891c81dd1052c4a

Remedy

https://github.com/tensorflow/tensorflow/security/advisories/GHSA-x4qx-4fjv-hmw6

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2022-21738?

    CVE-2022-21738 has been classified as a high severity vulnerability due to its impact on system stability.

  • How do I fix CVE-2022-21738?

    To mitigate CVE-2022-21738, upgrade TensorFlow to version 2.7.1 or later.

  • What versions of TensorFlow are affected by CVE-2022-21738?

    CVE-2022-21738 affects TensorFlow versions prior to 2.7.1, including those between 2.5.2 and 2.6.2.

  • What systems are at risk from CVE-2022-21738?

    Any system running the vulnerable versions of TensorFlow, particularly those utilizing the `SparseCountSparseOutput` function, is at risk.

  • What type of vulnerability is CVE-2022-21738?

    CVE-2022-21738 is an integer overflow vulnerability that can lead to the crashing of a TensorFlow process.

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203