CVE-2022-23592

Out of bounds read 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.

TensorFlow's type inference can cause a heap OOB read as the bounds checking is done in a DCHECK (which is a no-op during production):

if (node_t.type_id() != TFT_UNSET) {
  int ix = input_idx[i];
  DCHECK(ix < node_t.args_size())
      << "input " << i << " should have an output " << ix
      << " but instead only has " << node_t.args_size()
      << " outputs: " << node_t.DebugString();
  input_types.emplace_back(node_t.args(ix));
  // ...
}       

An attacker can control input_idx such that ix would be larger than the number of values in node_t.args.

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

CVE-2022-23592 has a CVSS score of 8.1 (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.8.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

We have patched the issue in GitHub commit c99d98cd189839dcf51aee94e7437b54b31f8abd.

The fix will be included in TensorFlow 2.8.0. This is the only affected version.

1. What is CVE-2022-23592? CVE-2022-23592 is a high-severity out-of-bounds read vulnerability in tensorflow (pip), affecting versions = 2.8.0-rc0. It is fixed in 2.8.0. A read operation accesses a memory location beyond the intended buffer boundary.
2. How severe is CVE-2022-23592? CVE-2022-23592 has a CVSS score of 8.1 (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-23592?
   • tensorflow (pip) (versions = 2.8.0-rc0)
   • tensorflow-cpu (pip) (versions = 2.8.0-rc0)
   • tensorflow-gpu (pip) (versions = 2.8.0-rc0)
4. Is there a fix for CVE-2022-23592? Yes. CVE-2022-23592 is fixed in 2.8.0. Upgrade to this version or later.
5. Is CVE-2022-23592 exploitable, and should I be worried? Whether CVE-2022-23592 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-23592 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-23592?
   • Upgrade tensorflow to 2.8.0 or later
   • Upgrade tensorflow-cpu to 2.8.0 or later
   • Upgrade tensorflow-gpu to 2.8.0 or later

Other vulnerabilities in tensorflow