CVE-2022-23576

CVE-2022-23576 is a high-severity integer overflow or wraparound vulnerability in tensorflow (pip), affecting versions < 2.5.3. It is fixed in 2.5.3, 2.6.3, 2.7.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Integer overflow in Tensorflow

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Impact

The implementation of OpLevelCostEstimator::CalculateOutputSize is vulnerable to an integer overflow if an attacker can create an operation which would involve tensors with large enough number of elements:

for (const auto& dim : output_shape.dim()) {
  output_size *= dim.size();
} 

Here, we can have a large enough number of dimensions in output_shape.dim() or just a small number of dimensions being large enough to cause an overflow in the multiplication.

An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value. Typical impact: incorrect size calculations leading to heap overflows or logic errors.

CVE-2022-23576 has a CVSS score of 6.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.5.3, 2.6.3, 2.7.1); upgrading removes the vulnerable code path.

Affected versions

tensorflow (< 2.5.3) tensorflow (>= 2.6.0, < 2.6.3) tensorflow (= 2.7.0) tensorflow-cpu (< 2.5.3) tensorflow-cpu (>= 2.6.0, < 2.6.3) tensorflow-cpu (= 2.7.0) tensorflow-gpu (< 2.5.3) tensorflow-gpu (>= 2.6.0, < 2.6.3) tensorflow-gpu (= 2.7.0)

Security releases

tensorflow → 2.5.3 (pip) tensorflow → 2.6.3 (pip) tensorflow → 2.7.1 (pip) tensorflow-cpu → 2.5.3 (pip) tensorflow-cpu → 2.6.3 (pip) tensorflow-cpu → 2.7.1 (pip) tensorflow-gpu → 2.5.3 (pip) tensorflow-gpu → 2.6.3 (pip) tensorflow-gpu → 2.7.1 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

We have patched the issue in GitHub commit b9bd6cfd1c50e6807846af9a86f9b83cafc9c8ae.

The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.

Frequently Asked Questions

  1. What is CVE-2022-23576? CVE-2022-23576 is a high-severity integer overflow or wraparound vulnerability in tensorflow (pip), affecting versions < 2.5.3. It is fixed in 2.5.3, 2.6.3, 2.7.1. An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value.
  2. How severe is CVE-2022-23576? CVE-2022-23576 has a CVSS score of 6.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which packages are affected by CVE-2022-23576?
    • tensorflow (pip) (versions < 2.5.3)
    • tensorflow-cpu (pip) (versions < 2.5.3)
    • tensorflow-gpu (pip) (versions < 2.5.3)
  4. Is there a fix for CVE-2022-23576? Yes. CVE-2022-23576 is fixed in 2.5.3, 2.6.3, 2.7.1. Upgrade to this version or later.
  5. Is CVE-2022-23576 exploitable, and should I be worried? Whether CVE-2022-23576 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2022-23576 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2022-23576?
    • Upgrade tensorflow to 2.5.3 or later
    • Upgrade tensorflow to 2.6.3 or later
    • Upgrade tensorflow to 2.7.1 or later
    • Upgrade tensorflow-cpu to 2.5.3 or later
    • Upgrade tensorflow-cpu to 2.6.3 or later
    • Upgrade tensorflow-cpu to 2.7.1 or later
    • Upgrade tensorflow-gpu to 2.5.3 or later
    • Upgrade tensorflow-gpu to 2.6.3 or later
    • Upgrade tensorflow-gpu to 2.7.1 or later

Other vulnerabilities in tensorflow

Stop the waste.
Protect your environment with Kodem.