CVE-2021-29610: Invalid validation in `QuantizeAndDequantizeV2`

Published May 14, 2021
·
Updated

Impact The validation in tf.rawops.QuantizeAndDequantizeV2 allows invalid values for axis argument:

python import tensorflow as tf

inputtensor = tf.constant([0.0], shape=[1], dtype=float) inputmin = tf.constant(-10.0) inputmax = tf.constant(-10.0)

tf.rawops.QuantizeAndDequantizeV2( input=inputtensor, inputmin=inputmin, inputmax=inputmax, signedinput=False, numbits=1, rangegiven=False, roundmode='HALFTOEVEN', narrowrange=False, axis=-2)

The validation uses || to mix two different conditions:

cc OPREQUIRES(ctx, (axis == -1 || axis < input.shape().dims()), errors::InvalidArgument(...));

If axis < -1 the condition in OPREQUIRES will still be true, but this value of axis results in heap underflow. This allows attackers to read/write to other data on the heap.

Patches We have patched the issue in GitHub commit c5b0d5f8ac19888e46ca14b0e27562e7fbbee9a9.

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 Yakun Zhang and Ying Wang of Baidu X-Team.

Other sources

TensorFlow is an end-to-end open source platform for machine learning. The validation in tf.rawops.QuantizeAndDequantizeV2 allows invalid values for axis argument:. The validation(https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/quantizeanddequantizeop.cc#L74-L77) uses || to mix two different conditions. If axis < -1 the condition in OPREQUIRES will still be true, but this value of axis results in heap underflow. This allows attackers to read/write to other data on the heap. 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.

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:20 PM
Data Sourced
via MITRE·07:20 PM
DescriptionSeverityWeakness
May 21, 2021
Advisory Published
via GitHub·02:28 PM

Frequently Asked Questions

1

What is the severity of CVE-2021-29610?

CVE-2021-29610 is classified as a medium severity vulnerability.

2

How do I fix CVE-2021-29610?

To address CVE-2021-29610, upgrade to TensorFlow version 2.4.2 or later.

3

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

CVE-2021-29610 affects TensorFlow versions prior to 2.1.4, between 2.2.0 and 2.2.3, between 2.3.0 and 2.3.3, and between 2.4.0 and 2.4.2.

4

What components are vulnerable in CVE-2021-29610?

The vulnerability exists in the tf.raw_ops.QuantizeAndDequantizeV2 operation of TensorFlow.

5

Is CVE-2021-29610 a remote code execution vulnerability?

CVE-2021-29610 is not a remote code execution vulnerability; it is related to input validation issues.

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