CVE-2023-25801

TensorFlow has double free in Fractional(Max/Avg)Pool

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 was reported by dmc1778, of [email protected].

nn_ops.fractional_avg_pool_v2 and nn_ops.fractional_max_pool_v2 require the first and fourth elements of their parameter pooling_ratio to be equal to 1.0, as pooling on batch and channel dimensions is not supported.

import tensorflow as tf
import os
import numpy as np
from tensorflow.python.ops import nn_ops
try:
  arg_0_tensor = tf.random.uniform([3, 30, 50, 3], dtype=tf.float64)
  arg_0 = tf.identity(arg_0_tensor)
  arg_1_0 = 2
  arg_1_1 = 3
  arg_1_2 = 1
  arg_1_3 = 1
  arg_1 = [arg_1_0,arg_1_1,arg_1_2,arg_1_3,]
  arg_2 = True
  arg_3 = True
  seed = 341261001
  out = nn_ops.fractional_avg_pool_v2(arg_0,arg_1,arg_2,arg_3,seed=seed,)
except Exception as e:
  print("Error:"+str(e))

CVE-2023-25801 has a CVSS score of 8.0 (High). The vector is requires local access, 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 ee50d1e00f81f62a4517453f721c634bbb478307.

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-25801? CVE-2023-25801 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-25801? CVE-2023-25801 has a CVSS score of 8.0 (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-25801?
   • 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-25801? Yes. CVE-2023-25801 is fixed in 2.11.1. Upgrade to this version or later.
5. Is CVE-2023-25801 exploitable, and should I be worried? Whether CVE-2023-25801 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-25801 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-25801?
   • 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