Description
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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| tensorflow | tensorflow | < 1.15.4, >= 2.0.0, < 2.0.3, >= 2.1.0, < 2.1.2, >= 2.2.0, < 2.2.1, >= 2.3.0, < 2.3.1 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
openSUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| openSUSE Leap 15.2 | tensorflow2 +3 | 2.1.2-lp152.7.3.1 | openSUSE-SU-2020:1766-1 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| PyPI | tensorflow | < 1.15.4 | 1.15.4 | GHSA-q4qf-3fc6-8x34 |
| PyPI | tensorflow | >= 2.0.0, < 2.0.3 | 2.0.3 | GHSA-q4qf-3fc6-8x34 |
| PyPI | tensorflow | >= 2.1.0, < 2.1.2 | 2.1.2 | GHSA-q4qf-3fc6-8x34 |
| PyPI | tensorflow | >= 2.2.0, < 2.2.1 | 2.2.1 | GHSA-q4qf-3fc6-8x34 |
| PyPI | tensorflow | >= 2.3.0, < 2.3.1 | 2.3.1 | GHSA-q4qf-3fc6-8x34 |
| PyPI | tensorflow | < 1.15.4 · >= 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.3, 2.1.2, 2.2.1, 2.3.1 | PYSEC-2020-130 |
| PyPI | tensorflow-cpu | < 1.15.4 | 1.15.4 | GHSA-q4qf-3fc6-8x34 |
| PyPI | tensorflow-cpu | >= 2.0.0, < 2.0.3 | 2.0.3 | GHSA-q4qf-3fc6-8x34 |
| PyPI | tensorflow-cpu | >= 2.1.0, < 2.1.2 | 2.1.2 | GHSA-q4qf-3fc6-8x34 |
| PyPI | tensorflow-cpu | >= 2.2.0, < 2.2.1 | 2.2.1 | GHSA-q4qf-3fc6-8x34 |
| PyPI | tensorflow-cpu | >= 2.3.0, < 2.3.1 | 2.3.1 | GHSA-q4qf-3fc6-8x34 |
| PyPI | tensorflow-cpu | < 1.15.4 · >= 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.3, 2.1.2, 2.2.1, 2.3.1 | PYSEC-2020-287 |
| PyPI | tensorflow-gpu | < 1.15.4 | 1.15.4 | GHSA-q4qf-3fc6-8x34 |
| PyPI | tensorflow-gpu | >= 2.0.0, < 2.0.3 | 2.0.3 | GHSA-q4qf-3fc6-8x34 |
| PyPI | tensorflow-gpu | >= 2.1.0, < 2.1.2 | 2.1.2 | GHSA-q4qf-3fc6-8x34 |
| PyPI | tensorflow-gpu | >= 2.2.0, < 2.2.1 | 2.2.1 | GHSA-q4qf-3fc6-8x34 |
| PyPI | tensorflow-gpu | >= 2.3.0, < 2.3.1 | 2.3.1 | GHSA-q4qf-3fc6-8x34 |
| PyPI | tensorflow-gpu | < 1.15.4 · >= 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.3, 2.1.2, 2.2.1, 2.3.1 | PYSEC-2020-322 |
Advisories 1
- openSUSE-SU-2020:1766-1 Security update for tensorflow2 SUSE / openSUSE Security Updates · Feb 4, 2026