Division by 0 in `QuantizedBatchNormWithGlobalNormalization`
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 runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc) does not validate all constraints specified in the op's contract(https://www.tensorflow.org/api_docs/python/tf/raw_ops/QuantizedBatchNormWithGlobalNormalization). The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
From the CVE record · GitHub_M
TensorFlow’s `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization` does not validate all constraints in its contract. An attacker who can supply inputs to the operation can trigger a division-by-zero error and cause a denial of service. The input does not specify network access, authentication, or user-interaction requirements.
Check installations of the PyPI packages tensorflow, tensorflow-cpu, or tensorflow-gpu in versions below 2.1.4, from 2.2.0 to below 2.2.3, from 2.3.0 to below 2.3.3, or from 2.4.0 to below 2.4.2.