| 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 |
To mimic Python's indexing with negative values, TFLite uses ResolveAxis to convert negative values to positive indices. However, the only check that the converted index is now valid is only present in debug builds:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/reference/reduce.h#L68-L72
If the DCHECK does not trigger, then code execution moves ahead with a negative index. This, in turn, results in accessing data out of bounds which results in segfaults and/or data corruption.
We have patched the issue in 2d88f470dea2671b430884260f3626b1fe99830a 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.
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 reported by members of the Aivul Team from Qihoo 360.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free