Skip to content
Fencer Intel
critical 9.0

CVE-2020-15205 json

Data leak in Tensorflow

published 6y ago modified 2mo ago also BIT-tensorflow-2020-15205 , EUVD-2020-0201 , GHSA-g7p5-5759-qv46 , PYSEC-2020-128 , PYSEC-2020-285 , PYSEC-2020-320

cvss
9.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `data_splits` argument of `tf.raw_ops.StringNGrams` lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after `ee ff` are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR. The issue is patched in commit 0462de5b544ed4731aa2fb23946ac22c01856b80, 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

Is CVE-2020-15205 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

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

Exploits and checks

  • github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-g7p5-5759-qv46 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 9.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
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

Weakness
  • CWE-122 Heap-based Buffer Overflow
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
  • CWE-787 Out-of-bounds Write

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.