CVE-2022-23574: Out of bounds read and write in Tensorflow

Published Feb 4, 2022
·
Updated

Impact There is a typo in TensorFlow's SpecializeType which results in heap OOB read/write:

cc for (int i = 0; i < opdef.outputargsize(); i++) { // ... for (int j = 0; j < t->argssize(); j++) { auto arg = t->mutableargs(i); // ... } }

Due to a typo, arg is initialized to the ith mutable argument in a loop where the loop index is j. Hence it is possible to assign to arg from outside the vector of arguments. Since this is a mutable proto value, it allows both read and write to outside of bounds data.

Patches We have patched the issue in GitHub commit 0657c83d08845cc434175934c642299de2c0f042.

The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.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.

Other sources

Tensorflow is an Open Source Machine Learning Framework. There is a typo in TensorFlow's SpecializeType which results in heap OOB read/write. Due to a typo, arg is initialized to the ith mutable argument in a loop where the loop index is j. Hence it is possible to assign to arg from outside the vector of arguments. Since this is a mutable proto value, it allows both read and write to outside of bounds data. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.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 4, 2022
CVE Published
via MITRE·10:32 PM
Data Sourced
via MITRE·10:32 PM
DescriptionSeverityWeakness
Feb 9, 2022
Advisory Published
via GitHub·11:25 PM

Frequently Asked Questions

1

What is the severity of CVE-2022-23574?

CVE-2022-23574 has a medium severity rating due to its potential for heap out-of-bounds read/write vulnerabilities.

2

How do I fix CVE-2022-23574?

To address CVE-2022-23574, upgrade to TensorFlow versions 2.5.3, 2.6.3, or 2.7.1 or later.

3

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

TensorFlow versions prior to 2.5.3, 2.6.3 (from 2.6.0 to 2.6.2), and 2.7.0 are affected by CVE-2022-23574.

4

What type of vulnerability is CVE-2022-23574?

CVE-2022-23574 is a heap out-of-bounds read/write vulnerability caused by a typo in TensorFlow's code.

5

Is CVE-2022-23574 related to TensorFlow's SpecializeType functionality?

Yes, CVE-2022-23574 is directly related to a typo in TensorFlow's SpecializeType function.

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