CVE-2021-29599: Division by zero in TFLite's implementation of `Split`

Published May 14, 2021
·
Updated

Impact The implementation of the Split TFLite operator is vulnerable to a division by zero error:

cc TFLITEENSUREMSG(context, inputsize % numsplits == 0, "Not an even split"); const int slicesize = inputsize / numsplits;

An attacker can craft a model such that numsplits would be 0.

Patches We have patched the issue in GitHub commit b22786e7e9b7bdb6a56936ff29cc7e9968d7bc1d.

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.

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 members of the Aivul Team from Qihoo 360.

Other sources

TensorFlow is an end-to-end open source platform for machine learning. The implementation of the Split TFLite operator is vulnerable to a division by zero error(https://github.com/tensorflow/tensorflow/blob/e2752089ef7ce9bcf3db0ec618ebd23ea119d0c7/tensorflow/lite/kernels/split.cc#L63-L65). An attacker can craft a model such that numsplits would be 0. 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.

MITRE

Affected Software

16 affected componentsFixes available
pip/tensorflow-gpu>=2.4.0<2.4.2
2.4.2
pip/tensorflow-gpu>=2.3.0<2.3.3
2.3.3
pip/tensorflow-gpu>=2.2.0<2.2.3
2.2.3
pip/tensorflow-gpu<2.1.4
2.1.4
pip/tensorflow-cpu>=2.4.0<2.4.2
2.4.2
pip/tensorflow-cpu>=2.3.0<2.3.3
2.3.3
pip/tensorflow-cpu>=2.2.0<2.2.3
2.2.3
pip/tensorflow-cpu<2.1.4
2.1.4
pip/tensorflow>=2.4.0<2.4.2
2.4.2
pip/tensorflow>=2.3.0<2.3.3
2.3.3
pip/tensorflow>=2.2.0<2.2.3
2.2.3
pip/tensorflow<2.1.4
2.1.4
Google TensorFlow<2.1.4
Google TensorFlow>=2.2.0<2.2.3
Google TensorFlow>=2.3.0<2.3.3
Google TensorFlow>=2.4.0<2.4.2

Event History

May 14, 2021
CVE Published
via MITRE·07:21 PM
Data Sourced
via MITRE·07:21 PM
DescriptionSeverityWeakness
May 21, 2021
Advisory Published
via GitHub·02:28 PM

Frequently Asked Questions

1

What is the severity of CVE-2021-29599?

CVE-2021-29599 has a medium severity due to its potential to cause a division by zero error, leading to application crashes.

2

How do I fix CVE-2021-29599?

To fix CVE-2021-29599, upgrade to TensorFlow versions 2.4.2, 2.3.3, 2.2.3, or 2.1.4.

3

Which versions of TensorFlow are affected by CVE-2021-29599?

CVE-2021-29599 affects TensorFlow versions up to 2.1.4 and between 2.2.0 and 2.4.2.

4

What is the nature of the vulnerability in CVE-2021-29599?

The nature of the vulnerability in CVE-2021-29599 pertains to a division by zero issue in the `Split` TFLite operator.

5

Can CVE-2021-29599 affect TensorFlow Lite applications?

Yes, CVE-2021-29599 can affect TensorFlow Lite applications that utilize the vulnerable `Split` operator implementation.

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