CVE-2023-25675

TensorFlow has Segfault in Bincount with XLA

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 r3pwnx of 360 AIVul Team

When running with XLA, tf.raw_ops.Bincount segfaults when given a parameter weights that is neither the same shape as parameter arr nor a length-0 tensor.

import tensorflow as tf

func = tf.raw_ops.Bincount
para={'arr': 6, 'size': 804, 'weights': [52, 351]}

@tf.function(jit_compile=True)
def fuzz_jit():
 y = func(**para)
 return y

print(fuzz_jit())

CVE-2023-25675 has a CVSS score of 7.5 (High). The vector is network-reachable, no 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.11.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

We have patched the issue in GitHub commit 8ae76cf085f4be26295d2ecf2081e759e04b8acf.

The fix will be included in TensorFlow 2.12. We will also cherrypick this commit on TensorFlow 2.11.1.

1. What is CVE-2023-25675? CVE-2023-25675 is a high-severity security vulnerability in tensorflow (pip), affecting versions < 2.11.1. It is fixed in 2.11.1.
2. How severe is CVE-2023-25675? CVE-2023-25675 has a CVSS score of 7.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-2023-25675?
   • tensorflow (pip) (versions < 2.11.1)
   • tensorflow-cpu (pip) (versions < 2.11.1)
   • tensorflow-gpu (pip) (versions < 2.11.1)
4. Is there a fix for CVE-2023-25675? Yes. CVE-2023-25675 is fixed in 2.11.1. Upgrade to this version or later.
5. Is CVE-2023-25675 exploitable, and should I be worried? Whether CVE-2023-25675 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-2023-25675 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-2023-25675?
   • Upgrade tensorflow to 2.11.1 or later
   • Upgrade tensorflow-cpu to 2.11.1 or later
   • Upgrade tensorflow-gpu to 2.11.1 or later

Other vulnerabilities in tensorflow