CVE-2021-37649: Null pointer dereference in `UncompressElement` in TensorFlow

Published Aug 12, 2021
·
Updated

Impact The code for tf.rawops.UncompressElement can be made to trigger a null pointer dereference:

python import tensorflow as tf

data = tf.data.Dataset.fromtensors([0.0]) tf.rawops.UncompressElement( compressed=tf.data.experimental.tovariant(data), outputtypes=[tf.int64], outputshapes=[2]) The implementation obtains a pointer to a CompressedElement from a Variant tensor and then proceeds to dereference it for decompressing. There is no check that the Variant tensor contained a CompressedElement, so the pointer is actually nullptr.

Patches We have patched the issue in GitHub commit 7bdf50bb4f5c54a4997c379092888546c97c3ebd.

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. The code for tf.rawops.UncompressElement can be made to trigger a null pointer dereference. The implementation obtains a pointer to a CompressedElement from a Variant tensor and then proceeds to dereference it for decompressing. There is no check that the Variant tensor contained a CompressedElement, so the pointer is actually nullptr. We have patched the issue in GitHub commit 7bdf50bb4f5c54a4997c379092888546c97c3ebd. 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 7bdf50bb4f5c54a4997c379092888546c97c3ebd
  11. Upgrade

    Upgrade TensorFlow 2.5.1 to a version that resolves this vulnerability.

    Patch 7bdf50bb4f5c54a4997c379092888546c97c3ebd
  12. Upgrade

    Upgrade TensorFlow 2.4.3 to a version that resolves this vulnerability.

    Patch 7bdf50bb4f5c54a4997c379092888546c97c3ebd
  13. Upgrade

    Upgrade TensorFlow 2.3.4 to a version that resolves this vulnerability.

    Patch 7bdf50bb4f5c54a4997c379092888546c97c3ebd

Event History

Aug 12, 2021
CVE Published
via MITRE·06:10 PM
Data Sourced
via MITRE·06:10 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 25, 2021
Advisory Published
via GitHub·02:43 PM

Frequently Asked Questions

1

What is the severity of CVE-2021-37649?

CVE-2021-37649 is classified as a medium severity vulnerability due to its potential to cause a null pointer dereference.

2

How do I fix CVE-2021-37649?

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

3

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

CVE-2021-37649 affects TensorFlow versions 2.3.0 to 2.3.4, 2.4.0 to 2.4.3, and 2.5.0.

4

What is the impact of CVE-2021-37649 on applications using TensorFlow?

The impact of CVE-2021-37649 is that it may lead to application crashes due to null pointer dereferences.

5

Is CVE-2021-37649 exploitable in production environments?

Yes, CVE-2021-37649 is potentially exploitable in production environments where affected TensorFlow versions are in use.

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