CVE-2021-37638: Null pointer dereference in `RaggedTensorToTensor` in TensorFlow

Published Aug 12, 2021
·
Updated

Impact Sending invalid argument for rowpartitiontypes of tf.rawops.RaggedTensorToTensor API results in a null pointer dereference and undefined behavior:

python import tensorflow as tf

tf.rawops.RaggedTensorToTensor( shape=1, values=10, defaultvalue=21, rowpartitiontensors=tf.constant([0,0,0,0]), rowpartitiontypes=[])

The implementation accesses the first element of a user supplied list of values without validating that the provided list is not empty.

Patches We have patched the issue in GitHub commit 301ae88b331d37a2a16159b65b255f4f9eb39314.

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. Sending invalid argument for rowpartitiontypes of tf.rawops.RaggedTensorToTensor API results in a null pointer dereference and undefined behavior. The implementation accesses the first element of a user supplied list of values without validating that the provided list is not empty. We have patched the issue in GitHub commit 301ae88b331d37a2a16159b65b255f4f9eb39314. 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 GitHub commit 301ae88b331d37a2a16159b65b255f4f9eb39314
  11. Upgrade

    Upgrade tensorflow to a version that resolves this vulnerability.

    Fixed in 2.5.1Patch GitHub commit 301ae88b331d37a2a16159b65b255f4f9eb39314
  12. Upgrade

    Upgrade tensorflow to a version that resolves this vulnerability.

    Fixed in 2.4.3Patch GitHub commit 301ae88b331d37a2a16159b65b255f4f9eb39314
  13. Upgrade

    Upgrade tensorflow to a version that resolves this vulnerability.

    Fixed in 2.3.4Patch GitHub commit 301ae88b331d37a2a16159b65b255f4f9eb39314

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:44 PM

Frequently Asked Questions

1

What is the severity of CVE-2021-37638?

CVE-2021-37638 has been classified with a severity rating that indicates a risk of null pointer dereference and undefined behavior.

2

How do I fix CVE-2021-37638?

To fix CVE-2021-37638, upgrade TensorFlow to version 2.5.1 or later.

3

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

CVE-2021-37638 affects TensorFlow versions 2.5.0, 2.4.0 to 2.4.3, and earlier than 2.3.4.

4

Is CVE-2021-37638 related to a specific API in TensorFlow?

Yes, CVE-2021-37638 is related to the `tf.raw_ops.RaggedTensorToTensor` API.

5

What kind of issues does CVE-2021-37638 cause in TensorFlow?

CVE-2021-37638 can cause a null pointer dereference leading to potential crashes and undefined behavior in TensorFlow applications.

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