CVE-2021-29617: Crash in `tf.strings.substr` due to `CHECK`-fail
Impact An attacker can cause a denial of service via CHECK-fail in tf.strings.substr with invalid arguments:
python import tensorflow as tf tf.strings.substr(input='abc', len=1, pos=[1,-1])
python import tensorflow as tf tf.strings.substr(input='abc', len=1, pos=[1,2])
Patches We have received a patch for the issue in GitHub commit 890f7164b70354c57d40eda52dcdd7658677c09f.
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 in #46900 and fixed in #46974.
Other sources
TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service via CHECK-fail in tf.strings.substr with invalid arguments. 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
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2021-29617?
CVE-2021-29617 has a severity level that can result in denial of service due to improper handling of invalid arguments in tf.strings.substr.
How do I fix CVE-2021-29617?
To fix CVE-2021-29617, update TensorFlow to version 2.4.2 or later.
Which versions of TensorFlow are affected by CVE-2021-29617?
CVE-2021-29617 affects TensorFlow versions prior to 2.4.2, including versions 2.1.4, 2.2.0 to 2.2.3, 2.3.0 to 2.3.3.
What is the impact of CVE-2021-29617?
The impact of CVE-2021-29617 is the potential for an attacker to cause a denial of service through an invalid argument in the tf.strings.substr function.
Is there a workaround for CVE-2021-29617?
There are no specific workarounds for CVE-2021-29617; upgrading to a patched version is the recommended solution.