Description
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can craft cases where this is larger than that of the second tensor. In turn, this would result in reads/writes outside of bounds since the interpreter will wrongly assume that there is enough data in both tensors. The issue is patched in commit 8ee24e7949a203d234489f9da2c5bf45a7d5157d, 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-mxjj-953w-2c2v |
| PyPI | tensorflow | >= 2.0.0, < 2.0.3 | 2.0.3 | GHSA-mxjj-953w-2c2v |
| PyPI | tensorflow | >= 2.1.0, < 2.1.2 | 2.1.2 | GHSA-mxjj-953w-2c2v |
| PyPI | tensorflow | >= 2.2.0, < 2.2.1 | 2.2.1 | GHSA-mxjj-953w-2c2v |
| PyPI | tensorflow | >= 2.3.0, < 2.3.1 | 2.3.1 | GHSA-mxjj-953w-2c2v |
| 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-131 |
| PyPI | tensorflow-cpu | < 1.15.4 | 1.15.4 | GHSA-mxjj-953w-2c2v |
| PyPI | tensorflow-cpu | >= 2.0.0, < 2.0.3 | 2.0.3 | GHSA-mxjj-953w-2c2v |
| PyPI | tensorflow-cpu | >= 2.1.0, < 2.1.2 | 2.1.2 | GHSA-mxjj-953w-2c2v |
| PyPI | tensorflow-cpu | >= 2.2.0, < 2.2.1 | 2.2.1 | GHSA-mxjj-953w-2c2v |
| PyPI | tensorflow-cpu | >= 2.3.0, < 2.3.1 | 2.3.1 | GHSA-mxjj-953w-2c2v |
| 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-288 |
| PyPI | tensorflow-gpu | < 1.15.4 | 1.15.4 | GHSA-mxjj-953w-2c2v |
| PyPI | tensorflow-gpu | >= 2.0.0, < 2.0.3 | 2.0.3 | GHSA-mxjj-953w-2c2v |
| PyPI | tensorflow-gpu | >= 2.1.0, < 2.1.2 | 2.1.2 | GHSA-mxjj-953w-2c2v |
| PyPI | tensorflow-gpu | >= 2.2.0, < 2.2.1 | 2.2.1 | GHSA-mxjj-953w-2c2v |
| PyPI | tensorflow-gpu | >= 2.3.0, < 2.3.1 | 2.3.1 | GHSA-mxjj-953w-2c2v |
| 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-323 |
Advisories 1
- openSUSE-SU-2020:1766-1 Security update for tensorflow2 SUSE / openSUSE Security Updates · Feb 4, 2026