CVE-2020-15207 json
Segfault and data corruption in tensorflow-lite
published 2020-09-25 6 y ago modified 2026-09-10 1 mo ago also BIT-tensorflow-2020-15207 , EUVD-2020-0203 , GHSA-q4qf-3fc6-8x34 , PYSEC-2020-130 , PYSEC-2020-287 , PYSEC-2020-322
- cvss
- 8.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- 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, 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.
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
1.24% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q4qf-3fc6-8x34 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H |
| GitHub | 3.1 | 8.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H |
| NVD | 3.1 | 9.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| OSV | 3.1 | 9.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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/2d88f470dea2671b430884260f3626b1fe99830a
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-q4qf-3fc6-8x34
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-15207
advisory, web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-287.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-322.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-130.yaml
web
-
github.com
/tensorflow/tensorflow
package
Sources
- CVE List CVE-2020-15207
- GitHub Advisory GHSA-q4qf-3fc6-8x34
- NVD CVE-2020-15207
- OSV BIT-tensorflow-2020-15207
- OSV PYSEC-2020-130
- OSV PYSEC-2020-287
- OSV PYSEC-2020-322
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.