CVE-2021-29512

Heap buffer overflow in RaggedBinCount

For more information

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

Attribution

This vulnerability has been reported by members of the Aivul Team from Qihoo 360.

If the splits argument of RaggedBincount does not specify a valid SparseTensor, then an attacker can trigger a heap buffer overflow:

import tensorflow as tf
tf.raw_ops.RaggedBincount(splits=[0], values=[1,1,1,1,1], size=5, weights=[1,2,3,4], binary_output=False)

This will cause a read from outside the bounds of the splits tensor buffer in the implementation of the RaggedBincount op:

    for (int idx = 0; idx < num_values; ++idx) {
      while (idx >= splits(batch_idx)) {
        batch_idx++;
      }
      ...
    }

Before the for loop, batch_idx is set to 0. The user controls the splits array, making it contain only one element, 0. Thus, the code in the while loop would increment batch_idx and then try to read splits(1), which is outside of bounds.

A write operation targets a memory location beyond the intended buffer boundary. Typical impact: memory corruption, crash, or arbitrary code execution.

CVE-2021-29512 has a CVSS score of 2.5 (Low). The vector is requires local access, 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.3.3, 2.4.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

We have patched the issue in GitHub commit eebb96c2830d48597d055d247c0e9aebaea94cd5.

The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3, as these are also affected.

1. What is CVE-2021-29512? CVE-2021-29512 is a low-severity out-of-bounds write vulnerability in tensorflow (pip), affecting versions >= 2.3.0, < 2.3.3. It is fixed in 2.3.3, 2.4.2. A write operation targets a memory location beyond the intended buffer boundary.
2. How severe is CVE-2021-29512? CVE-2021-29512 has a CVSS score of 2.5 (Low). 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-2021-29512?
   • tensorflow (pip) (versions >= 2.3.0, < 2.3.3)
   • tensorflow-cpu (pip) (versions >= 2.3.0, < 2.3.3)
   • tensorflow-gpu (pip) (versions >= 2.3.0, < 2.3.3)
4. Is there a fix for CVE-2021-29512? Yes. CVE-2021-29512 is fixed in 2.3.3, 2.4.2. Upgrade to this version or later.
5. Is CVE-2021-29512 exploitable, and should I be worried? Whether CVE-2021-29512 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-2021-29512 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-2021-29512?
   • Upgrade tensorflow to 2.3.3 or later
   • Upgrade tensorflow to 2.4.2 or later
   • Upgrade tensorflow-cpu to 2.3.3 or later
   • Upgrade tensorflow-cpu to 2.4.2 or later
   • Upgrade tensorflow-gpu to 2.3.3 or later
   • Upgrade tensorflow-gpu to 2.4.2 or later

Other vulnerabilities in tensorflow