CVE-2021-37637: TensorFlow - Null Pointer Dereference in CompressElement

tensorflow Updated 02 Oct 2025

Summary

06/03/2024
Yes i
Medium
Not published

CVE-2021-37637: Null pointer dereference in CompressElement 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-37637 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

TensorFlow is an end-to-end open source platform for machine learning. It provides a comprehensive ecosystem for building and deploying machine learning models. TensorFlow is widely used in various domains, including research, industry, and academia. This vulnerability affects versions 2.3.0 to 2.6.0-rc2 of TensorFlow.

Vulnerability Detail

The vulnerability (CVE-2021-37637) in TensorFlow allows an attacker to trigger a null pointer dereference by passing an invalid input to the tf.raw_ops.CompressElement function. The implementation of this function in the compression_utils.cc file did not properly validate the buffer obtained from a separate function call before accessing its size. This could lead to a crash or potential exploitation of the null pointer dereference. The issue has been patched in the GitHub commit 5dc7f6981fdaf74c8c5be41f393df705841fb7c5 and will be included in TensorFlow 2.6.0. The fix will also be backported to TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4.

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

There is no known workaround for this vulnerability. It is recommended to update TensorFlow to the patched versions as mentioned in the 'how_to_fix' section.

Conclusion

The vulnerability in TensorFlow (CVE-2021-37637) allows for a null pointer dereference when an invalid input is passed to the tf.raw_ops.CompressElement function. This can lead to crashes or potential exploitation. It is crucial to update TensorFlow to the patched versions (2.6.0, 2.5.1, 2.4.3, or 2.3.4) to mitigate this vulnerability. Regularly updating software dependencies is essential for maintaining the security of machine learning applications.

See every vulnerability recorded for tensorflow →

Share this vulnerability

FAQ

TensorFlow is an open source platform for machine learning, widely used for building and deploying machine learning models.

A null pointer dereference occurs when a program tries to access or manipulate memory using a null pointer, resulting in a crash or potential security vulnerability.

An attacker can exploit this vulnerability by passing an invalid input to the tf.raw_ops.CompressElement function in TensorFlow, triggering a null pointer dereference and potentially causing a crash or further exploitation.

No, only versions 2.3.0 to 2.6.0-rc2 of TensorFlow are affected by this vulnerability.

Yes, the vulnerability has been patched in the GitHub commit 5dc7f6981fdaf74c8c5be41f393df705841fb7c5. 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.

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