| Package | Affected versions | Patched versions |
|---|---|---|
| tensorflow | ≥ 2.0.0, < 2.0.3≥ 2.1.0, < 2.1.2≥ 2.2.0, < 2.2.1≥ 2.3.0, < 2.3.1< 1.15.4 | 2.0.32.1.22.2.12.3.11.15.4 |
| tensorflow-cpu | ≥ 2.0.0, < 2.0.3≥ 2.1.0, < 2.1.2≥ 2.2.0, < 2.2.1≥ 2.3.0, < 2.3.1< 1.15.4 | 2.0.32.1.22.2.12.3.11.15.4 |
| tensorflow-gpu | ≥ 2.0.0, < 2.0.3≥ 2.1.0, < 2.1.2≥ 2.2.0, < 2.2.1≥ 2.3.0, < 2.3.1< 1.15.4 | 2.0.32.1.22.2.12.3.11.15.4 |
| tensorflow | ≥ 2.0.0, < 2.0.3≥ 2.1.0, < 2.1.2≥ 2.2.0, < 2.2.1≥ 2.3.0, < 2.3.1< 1.15.4 | 2.0.32.1.22.2.12.3.11.15.4 |
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.
A potential workaround would be to add a custom Verifier to the model loading code to ensure that no operator reuses tensors as both inputs and outputs. Care should be taken to check all types of inputs (i.e., constant or variable tensors as well as optional tensors).
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
This vulnerability has been discovered from a variant analysis of GHSA-cvpc-8phh-8f45.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free