Division by zero in TFLite
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
≥ 2.6.0 · < 2.6.3≥ 2.7.0 · < 2.7.1
|
| tensorflow-gpu PyPI |
|
|
Tensorflow is an Open Source Machine Learning Framework. ### Impact An attacker can craft a TFLite model that would trigger a division by zero in the implementation of depthwise convolutions. The parameters of the convolution can be user controlled and are also used within a division operation to determine the size of the padding that needs to be added before applying the convolution. There is no check before this division that the divisor is strictly positive. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
From the CVE record · GitHub_M
TFLite depthwise convolutions can divide by zero when calculating padding from model-controlled parameters. An attacker can craft a TFLite model that triggers the flaw if an affected application processes it; the input does not specify network access or authentication requirements.
Check installations of the PyPI packages tensorflow, tensorflow-cpu, and tensorflow-gpu in versions below 2.5.3, from 2.6.0 to below 2.6.3, or from 2.7.0 to below 2.7.1.