CVE-2021-37661: Crash caused by integer conversion to unsigned in TensorFlow

Published Aug 12, 2021
·
Updated

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

15 affected componentsFixes available
pip/tensorflow-gpu=2.5.0
2.5.1
pip/tensorflow-gpu>=2.4.0<2.4.3
2.4.3
pip/tensorflow-gpu<2.3.4
2.3.4
pip/tensorflow-cpu=2.5.0
2.5.1
pip/tensorflow-cpu>=2.4.0<2.4.3
2.4.3
pip/tensorflow-cpu<2.3.4
2.3.4
pip/tensorflow=2.5.0
2.5.1
pip/tensorflow>=2.4.0<2.4.3
2.4.3
pip/tensorflow<2.3.4
2.3.4
Google TensorFlow>=2.3.0<2.3.4
Google TensorFlow>=2.4.0<2.4.3
Google TensorFlow=2.5.0
Google TensorFlow=2.6.0-rc0
Google TensorFlow=2.6.0-rc1
Google TensorFlow=2.6.0-rc2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/tensorflow-gpu to a version that resolves this vulnerability.

    Fixed in 2.5.1
  2. Upgrade

    Upgrade pip/tensorflow-gpu to a version that resolves this vulnerability.

    Fixed in 2.4.3
  3. Upgrade

    Upgrade pip/tensorflow-gpu to a version that resolves this vulnerability.

    Fixed in 2.3.4
  4. Upgrade

    Upgrade pip/tensorflow-cpu to a version that resolves this vulnerability.

    Fixed in 2.5.1
  5. Upgrade

    Upgrade pip/tensorflow-cpu to a version that resolves this vulnerability.

    Fixed in 2.4.3
  6. Upgrade

    Upgrade pip/tensorflow-cpu to a version that resolves this vulnerability.

    Fixed in 2.3.4
  7. Upgrade

    Upgrade pip/tensorflow to a version that resolves this vulnerability.

    Fixed in 2.5.1
  8. Upgrade

    Upgrade pip/tensorflow to a version that resolves this vulnerability.

    Fixed in 2.4.3
  9. Upgrade

    Upgrade pip/tensorflow to a version that resolves this vulnerability.

    Fixed in 2.3.4
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.6.0
  12. Upgrade

    Upgrade TensorFlow 2.5.1 to a version that resolves this vulnerability.

    Patch 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992
  13. Upgrade

    Upgrade TensorFlow 2.4.3 to a version that resolves this vulnerability.

    Patch 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992
  14. Upgrade

    Upgrade TensorFlow 2.3.4 to a version that resolves this vulnerability.

    Patch 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992

Event History

Aug 12, 2021
CVE Published
via MITRE·09:05 PM
Data Sourced
via MITRE·09:05 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 25, 2021
Advisory Published
via GitHub·02:42 PM

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

Is there a patch for CVE-2021-37661?

Yes, the patch for CVE-2021-37661 is included in the fixed versions of TensorFlow.

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