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

tensorflow Updated 02 Oct 2025

Summary

06/03/2024
Yes i
Medium
Not published

CVE-2022-23583: CHECK-failures in binary ops 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-23583 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 Penetration testing for web, API and mobile 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. This vulnerability affects versions 2.5.2, 2.6.0, 2.6.1, and 2.7.0 of TensorFlow.

Vulnerability Detail

A malicious user can exploit this vulnerability by modifying a SavedModel in such a way that it triggers CHECK failures when any binary operation is performed. This occurs when the protobuf part corresponding to the tensor arguments is altered, causing the dtype to no longer match the expected dtype of the operation. As a result, the binary operator receives corrupted data due to type confusion, leading to a denial of service. While most cases result in silent failures, there have been instances where this vulnerability causes a CHECK crash, further exacerbating the denial of service.

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 currently no known workaround for this vulnerability. It is recommended to apply the official fix as soon as it is released.

Conclusion

The vulnerability in TensorFlow can lead to a denial of service if exploited by a malicious user. It is crucial for users to update their TensorFlow installations to the latest patched versions once they become available. 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 machine learning framework developed by Google. It provides a wide range of tools and resources for building and deploying machine learning models.

A SavedModel is a serialized format for storing TensorFlow models. It allows models to be easily loaded and used for inference or further training.

By modifying a SavedModel to trigger CHECK failures, a malicious user can cause a denial of service by corrupting the data passed to binary operators.

The primary consequence of this vulnerability is a denial of service, which can impact the availability and reliability of TensorFlow-based applications.

No, only versions 2.5.2, 2.6.0, 2.6.1, and 2.7.0 are affected. The vulnerability will be fixed in TensorFlow 2.8.0 and backported to earlier versions.

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