Segmentation fault in tensorflow-lite
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
2.3.1| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and will release patch releases for all versions between 1.15 and 2.3. We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
From the CVE record · GitHub_M
TensorFlow Lite can crash or corrupt memory when a saved model uses the same tensor as both the input and output of an operator. The outcome depends on the operator. The input does not specify how an attacker would supply such a model or whether authentication or user interaction is required.
Teams using PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu versions below 1.15.4, or versions 2.0.0–2.0.2, 2.1.0–2.1.1, 2.2.0, or 2.3.0, should check their deployments.