CVE-2022-21731: Type confusion leading to segfault in Tensorflow

Published Feb 3, 2022
·
Updated

Impact The implementation of shape inference for ConcatV2 can be used to trigger a denial of service attack via a segfault caused by a type confusion:

python import tensorflow as tf

@tf.function def test(): y = tf.rawops.ConcatV2( values=[[1,2,3],[4,5,6]], axis = 0xb500005b) return y

test()

The axis argument is translated into concatdim in the ConcatShapeHelper helper function. Then, a value for minrank is computed based on concatdim. This is then used to validate that the values tensor has at least the required rank:

cc int64t concatdim; if (concatdimt->dtype() == DTINT32) { concatdim = staticcast<int64t>(concatdimt->flat<int32>()(0)); } else { concatdim = concatdimt->flat<int64t>()(0); }

// Minimum required number of dimensions. const int minrank = concatdim < 0 ? -concatdim : concatdim + 1;

// ... ShapeHandle input = c->input(endvalueindex - 1); TFRETURNIFERROR(c->WithRankAtLeast(input, minrank, &input));

However, WithRankAtLeast receives the lower bound as a 64-bits value and then compares it against the maximum 32-bits integer value that could be represented:

cc Status InferenceContext::WithRankAtLeast(ShapeHandle shape, int64t rank, ShapeHandle out) { if (rank > kint32max) { return errors::InvalidArgument("Rank cannot exceed kint32max"); } // ... }

Due to the fact that minrank is a 32-bits value and the value of axis, the rank argument is a negative value, so the error check is bypassed.

Patches We have patched the issue in GitHub commit 08d7b00c0a5a20926363849f611729f53f3ec022.

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 implementation of shape inference for ConcatV2 can be used to trigger a denial of service attack via a segfault caused by a type confusion. The axis argument is translated into concatdim in the ConcatShapeHelper helper function. Then, a value for minrank is computed based on concatdim. This is then used to validate that the values tensor has at least the required rank. However, WithRankAtLeast receives the lower bound as a 64-bits value and then compares it against the maximum 32-bits integer value that could be represented. Due to the fact that minrank is a 32-bits value and the value of axis, the rank argument is a negative value, so the error check is bypassed. 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·11:37 AM
Data Sourced
via MITRE·11:37 AM
DescriptionSeverity
Feb 10, 2022
Advisory Published
via GitHub·12:19 AM

Frequently Asked Questions

1

What is the severity of CVE-2022-21731?

CVE-2022-21731 has a high severity rating as it can lead to a denial of service due to a segmentation fault.

2

How do I fix CVE-2022-21731?

To fix CVE-2022-21731, upgrade to TensorFlow versions 2.5.3, 2.6.3, or 2.7.1 as these versions contain the necessary patches.

3

Which versions of TensorFlow are affected by CVE-2022-21731?

CVE-2022-21731 affects TensorFlow versions 2.5.2 and earlier, as well as 2.6.0 and 2.6.1.

4

Is CVE-2022-21731 fixed in the latest version of TensorFlow?

Yes, CVE-2022-21731 is fixed in TensorFlow 2.7.1 and later versions.

5

Can CVE-2022-21731 be exploited remotely?

Yes, CVE-2022-21731 can be exploited remotely, leading to potential service disruptions.

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