CVE-2021-37661: Crash caused by integer conversion to unsigned in TensorFlow
Impact An attacker can cause a denial of service in boostedtreescreatequantilestreamresource by using negative arguments:
python import tensorflow as tf from tensorflow.python.ops import genboostedtreesops import numpy as np
v= tf.Variable([0.0, 0.0, 0.0, 0.0, 0.0]) genboostedtreesops.boostedtreescreatequantilestreamresource( quantilestreamresourcehandle = v.handle, epsilon = [74.82224], numstreams = [-49], maxelements = np.int32(586))
The implementation does not validate that numstreams only contains non-negative numbers. In turn, this results in using this value to allocate memory:
cc class BoostedTreesQuantileStreamResource : public ResourceBase { public: BoostedTreesQuantileStreamResource(const float epsilon, const int64 maxelements, const int64 numstreams) : arebucketsready(false), epsilon(epsilon), numstreams(numstreams), maxelements(maxelements) { streams.reserve(numstreams); ... } }
However, reserve receives an unsigned integer so there is an implicit conversion from a negative value to a large positive unsigned. This results in a crash from the standard library.
Patches We have patched the issue in GitHub commit 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992.
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 an attacker can cause a denial of service in boostedtreescreatequantilestreamresource by using negative arguments. The implementation does not validate that numstreams only contains non-negative numbers. In turn, this results in using this value to allocate memory. However, reserve receives an unsigned integer so there is an implicit conversion from a negative value to a large positive unsigned. This results in a crash from the standard library. We have patched the issue in GitHub commit 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992. 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 to a fixed release to a version that resolves this vulnerability.
Patch 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.6.0 - Upgrade
Upgrade
TensorFlow 2.5.1to a version that resolves this vulnerability.Patch 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992 - Upgrade
Upgrade
TensorFlow 2.4.3to a version that resolves this vulnerability.Patch 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992 - Upgrade
Upgrade
TensorFlow 2.3.4to a version that resolves this vulnerability.Patch 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992
Event History
Frequently Asked Questions
What is the severity of CVE-2021-37661?
CVE-2021-37661 has a medium severity rating due to its potential to cause denial of service.
How do I fix CVE-2021-37661?
To fix CVE-2021-37661, upgrade TensorFlow to versions 2.3.4, 2.4.3, or 2.5.1.
Which versions of TensorFlow are affected by CVE-2021-37661?
CVE-2021-37661 affects TensorFlow versions 2.3.0 to 2.3.4 and 2.4.0 to 2.4.3, along with specific 2.6.0 release candidates.
What kind of attack can CVE-2021-37661 facilitate?
CVE-2021-37661 can facilitate a denial of service attack by exploiting negative arguments in the boosted trees function.
Is there a patch for CVE-2021-37661?
Yes, the patch for CVE-2021-37661 is included in the fixed versions of TensorFlow.