CVE-2021-37670: TensorFlow - Out-of-Bounds Read Vulnerability

tensorflow Updated 02 Oct 2025

Summary

06/03/2024
Yes i
Medium
Not published

CVE-2021-37670: Heap OOB in UpperBound and LowerBound in TensorFlow. Affects tensorflow across 3 version ranges.

>= 2.3.0, < 2.3.4 >= 2.4.0, < 2.4.3 >= 2.5.0, < 2.5.1

Fixed in 2.3.4, 2.4.3 or 2.5.1, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2021-37670 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

TensorFlow is an end-to-end open source platform for machine learning. It provides a comprehensive ecosystem of tools, libraries, and resources for developing and deploying machine learning models. TensorFlow is widely used in various industries and research domains.

Vulnerability Detail

The vulnerability identified as CVE-2021-37670 affects TensorFlow versions 2.3.0 to 2.6.0-rc2. It allows an attacker to read from outside the bounds of heap allocated data by exploiting the tf.raw_ops.UpperBound and tf.raw_ops.LowerBound functions. The issue arises due to the lack of validation for the rank of the sorted_input argument. An attacker can exploit this vulnerability by sending specially crafted illegal arguments to these functions. The impact of this vulnerability can lead to information disclosure and potential exploitation of sensitive data.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 2.3.0, < 2.3.4 2.3.4
  • >= 2.4.0, < 2.4.3 2.4.3
  • >= 2.5.0, < 2.5.1 2.5.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

No specific workaround has been provided for this vulnerability. It is recommended to apply the official patch or update to the fixed versions of TensorFlow.

Conclusion

The identified vulnerability in TensorFlow can be mitigated by updating to the patched versions or applying the official patch. It is crucial for users to keep their TensorFlow installations up to date to ensure the security and integrity of their machine learning workflows. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tensorflow →

Share this vulnerability

FAQ

TensorFlow is an open source platform for machine learning that provides a comprehensive set of tools and resources for developing and deploying machine learning models.

The vulnerability allows an attacker to read from outside the bounds of heap allocated data, potentially leading to information disclosure and exploitation of sensitive data.

The vulnerability affects TensorFlow versions 2.3.0 to 2.6.0-rc2.

To fix this vulnerability, update your TensorFlow installation to the patched versions. The fix will be included in TensorFlow 2.6.0 and backported to TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4.

No specific workaround has been provided. It is recommended to apply the official patch or update to the fixed versions of TensorFlow.

Related vulnerabilities

Recent vulnerabilities recorded for tensorflow.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 2.3.0, < 2.3.4 2.3.4
  • >= 2.4.0, < 2.4.3 2.4.3
  • >= 2.5.0, < 2.5.1 2.5.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback