CVE-2022-29200: Missing validation causes denial of service in TensorFlow via `LSTMBlockCell`

Published May 20, 2022
·
Updated

Impact The implementation of tf.rawops.LSTMBlockCell does not fully validate the input arguments. This results in a CHECK-failure which can be used to trigger a denial of service attack:

python import tensorflow as tf

tf.rawops.LSTMBlockCell( x=tf.constant(0.837607, shape=[28,29], dtype=tf.float32), csprev=tf.constant(0, shape=[28,17], dtype=tf.float32), hprev=tf.constant(0.592631638, shape=[28,17], dtype=tf.float32), w=tf.constant(0.887386262, shape=[46,68], dtype=tf.float32), wci=tf.constant(0, shape=[], dtype=tf.float32), wcf=tf.constant(0, shape=[17], dtype=tf.float32), wco=tf.constant(0.592631638, shape=[28,17], dtype=tf.float32), b=tf.constant(0.75259006, shape=[68], dtype=tf.float32), forgetbias=1, cellclip=0, usepeephole=False) The code does not validate the ranks of any of the arguments to this API call. This results in CHECK-failures when the elements of the tensor are accessed. Patches We have patched the issue in GitHub commit 803404044ae7a1efac48ba82d74111fce1ddb09a. The fix will be included in TensorFlow 2.9.0. We will also cherrypick this commit on TensorFlow 2.8.1, TensorFlow 2.7.2, and TensorFlow 2.6.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 Neophytos Christou from Secure Systems Lab at Brown University.

Other sources

TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of tf.rawops.LSTMBlockCell does not fully validate the input arguments. This results in a CHECK-failure which can be used to trigger a denial of service attack. The code does not validate the ranks of any of the arguments to this API call. This results in CHECK-failures when the elements of the tensor are accessed. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.

Affected Software

18 affected componentsFixes available
pip/tensorflow-gpu>=2.8.0<2.8.1
2.8.1
pip/tensorflow-gpu>=2.7.0<2.7.2
2.7.2
pip/tensorflow-gpu<2.6.4
2.6.4
pip/tensorflow-cpu>=2.8.0<2.8.1
2.8.1
pip/tensorflow-cpu>=2.7.0<2.7.2
2.7.2
pip/tensorflow-cpu<2.6.4
2.6.4
pip/tensorflow>=2.8.0<2.8.1
2.8.1
pip/tensorflow>=2.7.0<2.7.2
2.7.2
pip/tensorflow<2.6.4
2.6.4
Google TensorFlow<2.6.4
Google TensorFlow>=2.7.0<2.7.2
Google TensorFlow=2.7.0-rc0
Google TensorFlow=2.7.0-rc1
Google TensorFlow=2.8.0
Google TensorFlow=2.8.0-rc0
Google TensorFlow=2.8.0-rc1
Google TensorFlow=2.9.0-rc0
Google TensorFlow=2.9.0-rc1

Event History

May 20, 2022
CVE Published
via MITRE·09:30 PM
Data Sourced
via MITRE·09:30 PM
DescriptionSeverityWeakness
May 24, 2022
Advisory Published
10:10 PM

Frequently Asked Questions

1

What is the severity of CVE-2022-29200?

CVE-2022-29200 has a severity rating that can lead to a potential denial of service condition due to input argument validation issues.

2

How do I fix CVE-2022-29200?

To fix CVE-2022-29200, upgrade TensorFlow to version 2.8.1, 2.7.2, or 2.6.4 depending on your current version.

3

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

CVE-2022-29200 affects TensorFlow versions prior to 2.6.4, and from 2.7.0 up to 2.8.0.

4

What impact does CVE-2022-29200 have on applications using TensorFlow?

CVE-2022-29200 can cause applications to experience unexpected crashes or denial of service due to unchecked input parameters.

5

Is CVE-2022-29200 related to LSTM operations in TensorFlow?

Yes, CVE-2022-29200 specifically involves the LSTMBlockCell implementation in TensorFlow, which does not fully validate input arguments.

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