CVE-2021-37659: Out of bounds read via null pointer dereference in TensorFlow

Published Aug 12, 2021
·
Updated

Impact An attacker can cause undefined behavior via binding a reference to null pointer in all binary cwise operations that don't require broadcasting (e.g., gradients of binary cwise operations):

python import tensorflow as tf

tf.rawops.SqrtGrad(y=[4, 16],dy=[]) The implementation assumes that the two inputs have exactly the same number of elements but does not check that. Hence, when the eigen functor executes it triggers heap OOB reads and undefined behavior due to binding to nullptr.

Patches We have patched the issue in GitHub commit 93f428fd1768df147171ed674fee1fc5ab8309ec.

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 undefined behavior via binding a reference to null pointer in all binary cwise operations that don't require broadcasting (e.g., gradients of binary cwise operations). The implementation assumes that the two inputs have exactly the same number of elements but does not check that. Hence, when the eigen functor executes it triggers heap OOB reads and undefined behavior due to binding to nullptr. We have patched the issue in GitHub commit 93f428fd1768df147171ed674fee1fc5ab8309ec. 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/tensorflow to a version that resolves this vulnerability.

    Fixed in 2.6.0Patch 93f428fd1768df147171ed674fee1fc5ab8309ec
  11. Upgrade

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

    Fixed in 2.5.1Patch 93f428fd1768df147171ed674fee1fc5ab8309ec
  12. Upgrade

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

    Fixed in 2.4.3Patch 93f428fd1768df147171ed674fee1fc5ab8309ec
  13. Upgrade

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

    Fixed in 2.3.4Patch 93f428fd1768df147171ed674fee1fc5ab8309ec

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 impact of CVE-2021-37659?

CVE-2021-37659 can lead to undefined behavior via a null pointer reference during specific binary operations in TensorFlow.

2

How do I fix CVE-2021-37659?

To fix CVE-2021-37659, upgrade TensorFlow to version 2.5.1 or later, or to version 2.4.3 or later for affected versions below 2.5.0.

3

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

CVE-2021-37659 affects TensorFlow versions from 2.3.0 to 2.3.4, 2.4.0 to 2.4.3, and specific release candidates of version 2.6.0.

4

Is CVE-2021-37659 a critical vulnerability?

CVE-2021-37659 is considered to have a moderate severity level due to the potential for undefined behavior.

5

What software does CVE-2021-37659 affect?

CVE-2021-37659 affects the Google TensorFlow software, especially versions 2.3.x, 2.4.x, and the specific 2.6.0 release candidates.

Company

Resources

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