Division by zero in TensorFlow Lite `tf.raw_ops.UnravelIndex`
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu 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. In affected versions an attacker can cause denial of service in applications serving models using `tf.raw_ops.UnravelIndex` by triggering a division by 0. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unravel_index_op.cc#L36) does not check that the tensor subsumed by `dims` is not empty. Hence, if one element of `dims` is 0, the implementation does a division by 0. We have patched the issue in GitHub commit a776040a5e7ebf76eeb7eb923bf1ae417dd4d233. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
From the CVE record · GitHub_M
TensorFlow’s `tf.raw_ops.UnravelIndex` can divide by zero when an element of `dims` is 0. An attacker who can trigger that input in an application serving models can cause a denial of service. The input does not specify whether network access, authentication, or user interaction is required.
Engineers running affected versions of the PyPI packages tensorflow, tensorflow-cpu, or tensorflow-gpu below 2.3.4, from 2.4.0 to below 2.4.3, or from 2.5.0 to below 2.5.1 should check their deployments.