Division by 0 in `DenseCountSparseOutput`
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.DenseCountSparseOutput`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/efff014f3b2d8ef6141da30c806faf141297eca1/tensorflow/core/kernels/count_ops.cc#L123-L127) computes a divisor value from user data but does not check that the result is 0 before doing the division. Since `data` is given by the `values` argument, `num_batch_elements` is 0. 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.
From the CVE record · GitHub_M
TensorFlow’s `tf.raw_ops.DenseCountSparseOutput` can divide by zero when a divisor computed from user-supplied values is zero. An attacker who can supply those values can trigger a floating-point runtime error and cause a denial of service. The input does not specify network access, authentication requirements, or user interaction.
Check installations of the PyPI packages tensorflow, tensorflow-cpu, and tensorflow-gpu in versions <2.1.4, >=2.2.0 <2.2.3, >=2.3.0 <2.3.3, or >=2.4.0 <2.4.2.