CVE-2021-37664: Heap OOB in boosted trees in TensorFlow

Published Aug 12, 2021
·
Updated

Impact An attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to BoostedTreesSparseCalculateBestFeatureSplit:

python import tensorflow as tf

tf.rawops.BoostedTreesSparseCalculateBestFeatureSplit( nodeidrange=[0,10], statssummaryindices=[[1, 2, 3, 0x1000000]], statssummaryvalues=[1.0], statssummaryshape=[1,1,1,1], l1=l2=[1.0], treecomplexity=[0.5], minnodeweight=[1.0], logitsdimension=3, splittype='inequality')

The implementation needs to validate that each value in statssummaryindices is in range. Patches We have patched the issue in GitHub commit e84c975313e8e8e38bb2ea118196369c45c51378. 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 read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to BoostedTreesSparseCalculateBestFeatureSplit. The implementation needs to validate that each value in statssummaryindices is in range. We have patched the issue in GitHub commit e84c975313e8e8e38bb2ea118196369c45c51378. 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 TensorFlow to a version that resolves this vulnerability.

    Fixed in 2.6.0Patch e84c975313e8e8e38bb2ea118196369c45c51378
  11. Upgrade

    Upgrade TensorFlow to a version that resolves this vulnerability.

    Fixed in 2.5.1Patch e84c975313e8e8e38bb2ea118196369c45c51378
  12. Upgrade

    Upgrade TensorFlow to a version that resolves this vulnerability.

    Fixed in 2.4.3Patch e84c975313e8e8e38bb2ea118196369c45c51378
  13. Upgrade

    Upgrade TensorFlow to a version that resolves this vulnerability.

    Fixed in 2.3.4Patch e84c975313e8e8e38bb2ea118196369c45c51378
  14. Configuration

    Update TensorFlow so the implementation of BoostedTreesSparseCalculateBestFeatureSplit validates that each value in stats_summary_indices is in range (as described for the stats_ops.cc change in commit e84c975313e8e8e38bb2ea118196369c45c51378).

    TensorFlow BoostedTreesSparseCalculateBestFeatureSplit (stats_ops.cc) stats_summary_indices range validation = validate each value in stats_summary_indices is in range

Event History

Aug 12, 2021
CVE Published
via MITRE·08:25 PM
Data Sourced
via MITRE·08:25 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-37664?

CVE-2021-37664 has been classified as a medium severity vulnerability due to potential memory corruption risks.

2

How do I fix CVE-2021-37664?

To mitigate CVE-2021-37664, upgrade TensorFlow to version 2.5.1 or later.

3

Which versions of TensorFlow are affected by CVE-2021-37664?

CVE-2021-37664 impacts TensorFlow versions from 2.3.0 to 2.6.0-rc2, specifically 2.3.0 to 2.3.4, 2.4.0 to 2.4.3, and the 2.5.0 release.

4

What could happen if CVE-2021-37664 is exploited?

If exploited, CVE-2021-37664 may allow attackers to read out-of-bounds memory, leading to potential information leaks.

5

Is there a known exploit for CVE-2021-37664?

As of now, there are no publicly known exploits specific to CVE-2021-37664, but the risk of exploitation remains.

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