CVE-2022-23571: TensorFlow - Denial of Service Vulnerability

tensorflow Updated 02 Oct 2025

Summary

06/03/2024
Yes i
Medium
Not published

CVE-2022-23571: Reachable Assertion in Tensorflow. Affects tensorflow across 3 version ranges.

< 2.5.3 >= 2.6.0, < 2.6.3 >= 2.7.0, < 2.7.1

Fixed in 2.5.3, 2.6.3 or 2.7.1, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2022-23571 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 open-source machine learning framework developed by Google. It provides a comprehensive ecosystem of tools, libraries, and resources for building and deploying machine learning models. TensorFlow is widely used in various domains, including research, industry, and academia. However, a vulnerability has been discovered in TensorFlow that can lead to denial of service attacks.

Vulnerability Detail

The vulnerability in TensorFlow arises when decoding a tensor from protobuf. In certain cases, a CHECK assertion can be invalidated based on user-controlled arguments if the tensors have an invalid dtype and 0 elements or an invalid shape. This vulnerability allows attackers to cause denial of services in TensorFlow processes. The impact of this vulnerability can be significant, as it can disrupt the availability of TensorFlow-based applications and systems.

How To Fix

Fixed versions by release line

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

  • < 2.5.3 2.5.3
  • >= 2.6.0, < 2.6.3 2.6.3
  • >= 2.7.0, < 2.7.1 2.7.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 specific workaround available for this vulnerability. The recommended course of action is to apply the provided fix or update TensorFlow to the latest patched versions.

Conclusion

The vulnerability in TensorFlow can lead to denial of service attacks and disrupt the availability of TensorFlow-based applications and systems. It is crucial to update TensorFlow to the latest patched versions as soon as they become available. Regularly checking for updates and promptly applying them is essential for maintaining the security and stability of TensorFlow-based systems. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tensorflow →

Share this vulnerability

FAQ

TensorFlow is an open-source machine learning framework developed by Google. It provides tools and resources for building and deploying machine learning models.

This vulnerability can lead to denial of service attacks in TensorFlow processes, potentially disrupting the availability of TensorFlow-based applications and systems.

The vulnerability affects TensorFlow versions 2.5.2, 2.6.0, 2.6.1, 2.6.2, and 2.7.0. The fix will be included in TensorFlow 2.8.0 and backported to TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3.

No, there is no specific workaround available for this vulnerability. It is recommended to update TensorFlow to the latest patched versions.

To update TensorFlow, you can use the package manager or the installation method you used initially. Check the official TensorFlow documentation for detailed instructions on updating the framework.

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.5.3 2.5.3
  • >= 2.6.0, < 2.6.3 2.6.3
  • >= 2.7.0, < 2.7.1 2.7.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