CVE-2021-37646: Bad alloc in `StringNGrams` caused by integer conversion in TensorFlow
Impact The implementation of tf.rawops.StringNGrams is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value.
python import tensorflow as tf
tf.rawops.StringNGrams( data=['',''], datasplits=[0,2], separator=' '100, ngramwidths=[-80,0,0,-60], leftpad=' ', rightpad=' ', padwidth=100, preserveshortsequences=False)
The implementation calls reserve on a tstring with a value that sometimes can be negative if user supplies negative ngramwidths. The reserve method calls TFTStringReserve which has an unsigned long argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer.
Patches We have patched the issue in GitHub commit c283e542a3f422420cfdb332414543b62fc4e4a5.
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.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 members of the Aivul Team from Qihoo 360.
Other sources
TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of tf.rawops.StringNGrams is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The implementation calls reserve on a tstring with a value that sometimes can be negative if user supplies negative ngramwidths. The reserve method calls TFTStringReserve which has an unsigned long argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer. We have patched the issue in GitHub commit c283e542a3f422420cfdb332414543b62fc4e4a5. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/tensorflow-gputo a version that resolves this vulnerability.Fixed in 2.5.1 - Upgrade
Upgrade
pip/tensorflow-gputo a version that resolves this vulnerability.Fixed in 2.4.3 - Upgrade
Upgrade
pip/tensorflow-gputo a version that resolves this vulnerability.Fixed in 2.3.4 - Upgrade
Upgrade
pip/tensorflow-cputo a version that resolves this vulnerability.Fixed in 2.5.1 - Upgrade
Upgrade
pip/tensorflow-cputo a version that resolves this vulnerability.Fixed in 2.4.3 - Upgrade
Upgrade
pip/tensorflow-cputo a version that resolves this vulnerability.Fixed in 2.3.4 - Upgrade
Upgrade
pip/tensorflowto a version that resolves this vulnerability.Fixed in 2.5.1 - Upgrade
Upgrade
pip/tensorflowto a version that resolves this vulnerability.Fixed in 2.4.3 - Upgrade
Upgrade
pip/tensorflowto a version that resolves this vulnerability.Fixed in 2.3.4 - Upgrade
Upgrade
tensorflow/tensorflowto a version that resolves this vulnerability.Fixed in 2.6.0 - Upgrade
Upgrade
tensorflow/tensorflowto a version that resolves this vulnerability.Patch c283e542a3f422420cfdb332414543b62fc4e4a5 - Upgrade
Upgrade
tensorflow/tensorflowto a version that resolves this vulnerability.Fixed in 2.5.1 - Upgrade
Upgrade
tensorflow/tensorflowto a version that resolves this vulnerability.Fixed in 2.4.3 - Upgrade
Upgrade
tensorflow/tensorflowto a version that resolves this vulnerability.Fixed in 2.3.4
Event History
Frequently Asked Questions
What is the severity of CVE-2021-37646?
CVE-2021-37646 has been assigned a high severity rating due to its potential to lead to integer overflow and memory corruption.
How do I fix CVE-2021-37646?
You can fix CVE-2021-37646 by upgrading to TensorFlow version 2.5.1 or later, or TensorFlow GPU version 2.4.3.
Which versions of TensorFlow are affected by CVE-2021-37646?
CVE-2021-37646 affects TensorFlow versions 2.3.0 to 2.3.4, 2.4.0 to 2.4.3, 2.5.0, and pre-release versions of 2.6.0.
What impact does CVE-2021-37646 have on applications using TensorFlow?
CVE-2021-37646 could result in application crashes or arbitrary code execution due to memory allocation issues.
Is there a CVE-2021-37646 workaround available?
There are no specific workarounds for CVE-2021-37646 other than applying the recommended updates.