CVE-2021-37673: `CHECK`-fail in `MapStage` in TensorFlow

Published Aug 12, 2021
·
Updated

Impact An attacker can trigger a denial of service via a CHECK-fail in tf.rawops.MapStage:

python import tensorflow as tf tf.rawops.MapStage( key=tf.constant([], shape=[0, 0, 0, 0], dtype=tf.int64), indices=tf.constant((0), dtype=tf.int32), values=[tf.constant((0), dtype=tf.int32)], dtypes=[tf.int32, tf.int64], capacity=0, memorylimit=0, container='', sharedname='') The implementation does not check that the key input is a valid non-empty tensor. Patches We have patched the issue in GitHub commit d7de67733925de196ec8863a33445b73f9562d1d.

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 Ying Wang and Yakun Zhang of Baidu X-Team.

Other sources

TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a denial of service via a CHECK-fail in tf.rawops.MapStage. The implementation does not check that the key input is a valid non-empty tensor. We have patched the issue in GitHub commit d7de67733925de196ec8863a33445b73f9562d1d. 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 GitHub commit d7de67733925de196ec8863a33445b73f9562d1d
  11. Upgrade

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

    Fixed in 2.5.1Patch GitHub commit d7de67733925de196ec8863a33445b73f9562d1d
  12. Upgrade

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

    Fixed in 2.4.3Patch GitHub commit d7de67733925de196ec8863a33445b73f9562d1d
  13. Upgrade

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

    Fixed in 2.3.4Patch GitHub commit d7de67733925de196ec8863a33445b73f9562d1d

Event History

Aug 12, 2021
CVE Published
via MITRE·10:55 PM
Data Sourced
via MITRE·10:55 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 25, 2021
Advisory Published
via GitHub·02:41 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2021-37673?

CVE-2021-37673 has been classified as a denial of service vulnerability.

2

How do I fix CVE-2021-37673?

To remediate CVE-2021-37673, upgrade to TensorFlow versions 2.3.4, 2.4.3, or 2.5.1.

3

What software is affected by CVE-2021-37673?

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

4

Can CVE-2021-37673 be exploited remotely?

Yes, CVE-2021-37673 can be exploited remotely to cause a denial of service.

5

What environment is vulnerable to CVE-2021-37673?

CVE-2021-37673 impacts environments using the specified vulnerable versions of TensorFlow.

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