CVE-2022-23569: Denial of Service Vulnerability in TensorFlow

tensorflow Updated 02 Oct 2025

Summary

06/03/2024
Yes i
Medium
Not published

CVE-2022-23569: CHECK-fails when building invalid tensor shapes 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-23569 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, multiple operations in TensorFlow can be exploited to trigger a denial of service vulnerability. This vulnerability, identified as CVE-2022-23569, allows an attacker to cause assertion failures, leading to a denial of service condition.

Vulnerability Detail

The vulnerability in TensorFlow arises from the failure of CHECK operations, which are used for assertion checks. By manipulating certain operations, an attacker can trigger these CHECK-fails, resulting in assertion failures and causing the TensorFlow application to crash. This vulnerability can be exploited remotely, without requiring any user interaction. The impact of this vulnerability is a denial of service, where the affected TensorFlow application becomes unresponsive or crashes, disrupting its normal functionality. The severity of this vulnerability is assessed as medium.

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 approach is to update the TensorFlow package to a fixed version as mentioned in the 'how_to_fix' section.

Conclusion

The vulnerability in TensorFlow (CVE-2022-23569) allows an attacker to trigger assertion failures, leading to a denial of service condition. To mitigate this vulnerability, it is crucial to update the TensorFlow package to one of the fixed versions: 2.8.0, 2.7.1, 2.6.3, or 2.5.3. This will ensure that the necessary patches are applied to prevent the exploitation of this vulnerability. For further assistance or support in 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 a comprehensive ecosystem of tools, libraries, and resources for building and deploying machine learning models.

The vulnerability allows an attacker to trigger assertion failures in TensorFlow, leading to a denial of service condition. This can result in the affected TensorFlow application becoming unresponsive or crashing.

To fix this vulnerability, update the TensorFlow package to one of the fixed versions: 2.8.0, 2.7.1, 2.6.3, or 2.5.3. Ensure that you are using the latest version of the package to incorporate the necessary patches.

No, there is no specific workaround available for this vulnerability. Updating the TensorFlow package to a fixed version is the recommended approach.

Yes, this vulnerability can be exploited remotely without requiring any user interaction.

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