Skip to content
Fencer Intel
medium 6.5

CVE-2020-15210 json

Segmentation fault in tensorflow-lite

published 6y ago modified 2mo ago also BIT-tensorflow-2020-15210 , EUVD-2020-0206 , GHSA-x9j7-x98r-r4w2 , PYSEC-2020-133 , PYSEC-2020-290 , PYSEC-2020-325

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
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, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and will release patch releases for all versions between 1.15 and 2.3. We recommend users to upgrade to TensorFlow 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

Is CVE-2020-15210 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.74% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-x9j7-x98r-r4w2 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:N/I:P/A:P
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/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

Weakness

References

Sources

Fencer Intel 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.