Segfault and data corruption 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, 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. 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. The issue is patched in commit 2d88f470dea2671b430884260f3626b1fe99830a, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
From the CVE record · GitHub_M
In non-debug builds, TFLite's ResolveAxis may allow an invalid negative index to reach an out-of-bounds data access. This can cause a segmentation fault or data corruption. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Engineers using PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu before 1.15.4, or in the 2.0.x, 2.1.x, 2.2.x, or 2.3.x lines before their respective fixed releases, should check their installations.