CVE-2022-36015

TensorFlow vulnerable to integer overflow in math ops

For more information

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

When RangeSize receives values that do not fit into an int64_t, it crashes.

  auto size = (std::is_integral<T>::value
                   ? ((Eigen::numext::abs(limit - start) +
                       Eigen::numext::abs(delta) - T(1)) /
                      Eigen::numext::abs(delta))
                   : (Eigen::numext::ceil(
                         Eigen::numext::abs((limit - start) / delta))));

  // This check does not cover all cases.
  if (size > std::numeric_limits<int64_t>::max()) {
    return errors::InvalidArgument("Requires ((limit - start) / delta) <= ",
                                   std::numeric_limits<int64_t>::max());
  }

  c->set_output(0, c->Vector(static_cast<int64_t>(size)));
  return Status::OK();
}

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.

Kodem intelligence

Already deployed Kodem?

We have patched the issue in GitHub commit 37e64539cd29fcfb814c4451152a60f5d107b0f0.
The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range.

1. What is CVE-2022-36015? CVE-2022-36015 is a low-severity integer overflow or wraparound vulnerability in tensorflow (pip), affecting versions < 2.7.2. It is fixed in 2.7.2, 2.8.1, 2.9.1. An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value.
2. Which packages are affected by CVE-2022-36015?
   • tensorflow (pip) (versions < 2.7.2)
   • tensorflow-cpu (pip) (versions < 2.7.2)
   • tensorflow-gpu (pip) (versions < 2.7.2)
3. Is there a fix for CVE-2022-36015? Yes. CVE-2022-36015 is fixed in 2.7.2, 2.8.1, 2.9.1. Upgrade to this version or later.
4. Is CVE-2022-36015 exploitable, and should I be worried? Whether CVE-2022-36015 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
5. What actually determines whether CVE-2022-36015 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.
6. How do I fix CVE-2022-36015?
   • Upgrade tensorflow to 2.7.2 or later
   • Upgrade tensorflow to 2.8.1 or later
   • Upgrade tensorflow to 2.9.1 or later
   • Upgrade tensorflow-cpu to 2.7.2 or later
   • Upgrade tensorflow-cpu to 2.8.1 or later
   • Upgrade tensorflow-cpu to 2.9.1 or later
   • Upgrade tensorflow-gpu to 2.7.2 or later
   • Upgrade tensorflow-gpu to 2.8.1 or later
   • Upgrade tensorflow-gpu to 2.9.1 or later

Other vulnerabilities in tensorflow