CVE-2020-15208 json
Data corruption in tensorflow-lite
published 2020-09-25 6 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2020-15208 , EUVD-2020-0204 , GHSA-mxjj-953w-2c2v , PYSEC-2020-131 , PYSEC-2020-288 , PYSEC-2020-323
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi tensorflow 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1
- pypi tensorflow-cpu 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1
- pypi tensorflow-gpu 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1
- bitnami tensorflow 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1
- google tensorflow 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1
- tensorflow2 openSUSE Leap 15.2 2.1.2-lp152.7.3.1
- tensorflow2-lite openSUSE Leap 15.2 2.1.2-lp152.7.3.1
- tensorflow2_2_1_2-gnu-hpc openSUSE Leap 15.2 2.1.2-lp152.7.3.1
- tensorflow2_2_1_2-gnu-openmpi2-hpc openSUSE Leap 15.2 2.1.2-lp152.7.3.1
opensuse advisories openSUSE-SU-2020:1766-1
Exploit prediction
0.91% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mxjj-953w-2c2v referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| OSV | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| 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 |
| 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 |
| 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 |
| bitnami | 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 |
Affected products
- tensorflow tensorflow
Classification
References
-
github.com
/tensorflow/tensorflow/commit/8ee24e7949a203d234489f9da2c5bf45a7d5157d
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-mxjj-953w-2c2v
web, exploit, third-party-advisory, advisory
-
lists.opensuse.org
/opensuse-security-announce/2020-10/msg00065.html
vendor-advisory, web, mailing-list, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/releases/tag/v2.3.1
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-15208
advisory, web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-288.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-323.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-131.yaml
web
-
github.com
/tensorflow/tensorflow
package
Sources
- CVE List CVE-2020-15208
- GitHub Advisory GHSA-mxjj-953w-2c2v
- NVD CVE-2020-15208
- OSV BIT-tensorflow-2020-15208
- OSV PYSEC-2020-131
- OSV PYSEC-2020-288
- OSV PYSEC-2020-323
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.