CVE-2022-21736: Undefined behavior in Tensorflow

Published Feb 3, 2022
·
Updated

Impact The implementation of SparseTensorSliceDataset has an undefined behavior: under certain condition it can be made to dereference a nullptr value:

python import tensorflow as tf import numpy as np

tf.rawops.SparseTensorSliceDataset( indices=[[]], values=[], denseshape=[1,1])

The 3 input arguments represent a sparse tensor. However, there are some preconditions that these arguments must satisfy but these are not validated in the implementation.

Patches We have patched the issue in GitHub commit 965b97e4a9650495cda5a8c210ef6684b4b9eceb.

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 Faysal Hossain Shezan from University of Virginia.

Other sources

Tensorflow is an Open Source Machine Learning Framework. The implementation of SparseTensorSliceDataset has an undefined behavior: under certain condition it can be made to dereference a nullptr value. The 3 input arguments to SparseTensorSliceDataset represent a sparse tensor. However, there are some preconditions that these arguments must satisfy but these are not validated in the implementation. 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·12:08 PM
Data Sourced
via MITRE·12:08 PM
DescriptionSeverity
Feb 9, 2022
Advisory Published
via GitHub·11:43 PM

Frequently Asked Questions

1

What is the severity of CVE-2022-21736?

CVE-2022-21736 has a medium severity rating due to the potential for undefined behaviors affecting application stability.

2

How do I fix CVE-2022-21736?

To fix CVE-2022-21736, upgrade to TensorFlow version 2.7.1 or later, or apply the appropriate updates for earlier versions as specified.

3

What versions of TensorFlow are affected by CVE-2022-21736?

CVE-2022-21736 affects TensorFlow versions up to and including 2.7.0.

4

Is CVE-2022-21736 related to a specific feature in TensorFlow?

Yes, CVE-2022-21736 is related to the implementation of SparseTensorSliceDataset in TensorFlow.

5

What should I do if I'm using an affected version of TensorFlow?

If using an affected version of TensorFlow, it is recommended to update to a non-vulnerable version as soon as possible to mitigate the risk.

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