CVE-2021-29619: TensorFlow - Segfault in SparseCountSparseOutput

tensorflow Updated 02 Oct 2025

Summary

06/03/2024
Yes i
Medium
Not published

CVE-2021-29619: Segfault in tf.raw_ops.SparseCountSparseOutput. Affects tensorflow across 4 version ranges.

< 2.1.4 >= 2.2.0, < 2.2.3 >= 2.3.0, < 2.3.3 >= 2.4.0, < 2.4.2

Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓

Also tracked for

The same CVE-2021-29619 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. It offers a range of APIs and tools for data preprocessing, model training, and inference. However, a vulnerability has been discovered in TensorFlow that can lead to a segfault when passing invalid arguments to the tf.raw_ops.SparseCountSparseOutput function.

Vulnerability Detail

The vulnerability (CVE-2021-29619) in TensorFlow arises when invalid arguments are passed to the tf.raw_ops.SparseCountSparseOutput function. This issue can be triggered by fuzzing or other means of discovering invalid inputs. When these invalid arguments are processed, it results in a segfault, causing the application to crash. The impact of this vulnerability can be severe, as it can lead to denial of service or potential exploitation of other vulnerabilities in the system. The vulnerability affects multiple versions of TensorFlow, including 2.1.4, 2.2.3, 2.3.3, and 2.4.2.

How To Fix

Fixed versions by release line

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

  • < 2.1.4 2.1.4
  • >= 2.2.0, < 2.2.3 2.2.3
  • >= 2.3.0, < 2.3.3 2.3.3
  • >= 2.4.0, < 2.4.2 2.4.2

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

Workaround

As this vulnerability is related to passing invalid arguments to a specific function, there is no known workaround available. It is advised to follow the recommended fix and update to the patched version of TensorFlow as soon as it becomes available.

Conclusion

In conclusion, the vulnerability in TensorFlow (CVE-2021-29619) can lead to a segfault when passing invalid arguments to the tf.raw_ops.SparseCountSparseOutput function. This can result in a denial of service or potential exploitation of other vulnerabilities. It is crucial to update to the latest patched version of TensorFlow to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to 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 ecosystem for building and deploying machine learning models.

The vulnerability can lead to a segfault in TensorFlow, causing the application to crash. This can result in denial of service or potential exploitation of other vulnerabilities in the system.

The vulnerability affects TensorFlow versions 2.1.4, 2.2.3, 2.3.3, and 2.4.2.

No, there is no known workaround for this vulnerability. It is recommended to update to the patched version of TensorFlow as soon as it becomes available.

To fix this vulnerability, it is recommended to update to the latest patched version of TensorFlow. The fix will be included in TensorFlow 2.5.0, and updates will also be released for TensorFlow 2.4.2, 2.3.3, 2.2.3, and 2.1.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.1.4 2.1.4
  • >= 2.2.0, < 2.2.3 2.2.3
  • >= 2.3.0, < 2.3.3 2.3.3
  • >= 2.4.0, < 2.4.2 2.4.2

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