medium
5.5
CWE
369
Advisory Published
Advisory Published
Updated

CVE-2021-41218: Integer division by 0 in `tf.raw_ops.AllToAll`

First published: Fri Nov 05 2021(Updated: )

### Impact The [shape inference code for `AllToAll`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/tpu_cross_replica_ops.cc#L25-L74) can be made to execute a division by 0: ```python import tensorflow as tf @tf.function def func(): return tf.raw_ops.AllToAll( input=[0.0, 0.1652, 0.6543], group_assignment=[1, -1], concat_dimension=0, split_dimension=0, split_count=0) func() ``` This occurs whenever the `split_count` argument is 0: ```cc TF_RETURN_IF_ERROR(c->GetAttr("split_count", &split_count)); ... for (int32_t i = 0; i < rank; ++i) { ... dims[i] = c->MakeDim(c->Value(dims[i]) / split_count); ... } ``` ### Patches We have patched the issue in GitHub commit [a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc](https://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc). The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, 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 members of the Aivul Team from Qihoo 360.

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

Affected SoftwareAffected VersionHow to fix
pip/tensorflow-gpu<2.4.4
2.4.4
pip/tensorflow-gpu>=2.5.0<2.5.2
2.5.2
pip/tensorflow-gpu>=2.6.0<2.6.1
2.6.1
pip/tensorflow-cpu<2.4.4
2.4.4
pip/tensorflow-cpu>=2.5.0<2.5.2
2.5.2
pip/tensorflow-cpu>=2.6.0<2.6.1
2.6.1
pip/tensorflow<2.4.4
2.4.4
pip/tensorflow>=2.5.0<2.5.2
2.5.2
pip/tensorflow>=2.6.0<2.6.1
2.6.1
TensorFlow Keras>=2.4.0<2.4.4
TensorFlow Keras>=2.6.0<2.6.1
TensorFlow Keras=2.7.0-rc0
TensorFlow Keras=2.7.0-rc1

Remedy

https://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc

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-2021-41218?

    CVE-2021-41218 is classified with a medium severity due to the potential for a division by zero which can lead to application crashes.

  • How do I fix CVE-2021-41218?

    To fix CVE-2021-41218, upgrade to TensorFlow version 2.4.4, 2.5.2, or 2.6.1 as appropriate for your installation.

  • Which versions of TensorFlow are affected by CVE-2021-41218?

    CVE-2021-41218 affects TensorFlow versions 2.4.0 to 2.4.4, 2.6.0 to 2.6.1, and the 2.7.0 release candidates.

  • Is CVE-2021-41218 a critical vulnerability?

    CVE-2021-41218 is not considered a critical vulnerability but still requires attention due to its impact on application stability.

  • What happens if I do not address CVE-2021-41218?

    If CVE-2021-41218 is not addressed, applications using vulnerable versions of TensorFlow may experience crashes during execution.

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