CVE-2020-15205: Data leak in Tensorflow

CVE-2020-15205 · Severity: low · CVSS 3.1 · Published 2020-09-25

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.

Technologies: tensorflow (PyPI), tensorflow-cpu (PyPI), tensorflow-gpu (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2020-15205 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-15205 being exploited in the wild.
How severe is CVE-2020-15205?
Low severity, with a CVSS score of 3.1, published 25 September 2020.
Which products and versions are affected?
tensorflow (PyPI) ECOSYSTEM:introduced=0,fixed=1.15.4, GIT:introduced=0,fixed=0462de5b544ed4731aa2fb23946ac22c01856b80|ECOSYSTEM:introduced=0,fixed=1.15.4,introduced=2.0.0,fixed=2.0.3,introduced=2.1.0,fixed=2.1.2,introduced=2.2.0,fixed=2.2.1,introduced=2.3.0,fixed=2.3.1; tensorflow-cpu (PyPI) ECOSYSTEM:introduced=0,fixed=1.15.4, GIT:introduced=0,fixed=0462de5b544ed4731aa2fb23946ac22c01856b80|ECOSYSTEM:introduced=0,fixed=1.15.4,introduced=2.0.0,fixed=2.0.3,introduced=2.1.0,fixed=2.1.2,introduced=2.2.0,fixed=2.2.1,introduced=2.3.0,fixed=2.3.1; tensorflow-gpu (PyPI) ECOSYSTEM:introduced=0,fixed=1.15.4, GIT:introduced=0,fixed=0462de5b544ed4731aa2fb23946ac22c01856b80|ECOSYSTEM:introduced=0,fixed=1.15.4,introduced=2.0.0,fixed=2.0.3,introduced=2.1.0,fixed=2.1.2,introduced=2.2.0,fixed=2.2.1,introduced=2.3.0,fixed=2.3.1.
Is there a fix for CVE-2020-15205?
Yes. tensorflow (PyPI): upgrade to 1.15.4, 2.3.1 or later; tensorflow-cpu (PyPI): upgrade to 1.15.4, 2.3.1 or later; tensorflow-gpu (PyPI): upgrade to 1.15.4, 2.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-15205?
Check whether you run tensorflow (PyPI), tensorflow-cpu (PyPI) or tensorflow-gpu (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • tensorflow (PyPI): upgrade to 1.15.4, 2.3.1 or later
    pip install "tensorflow>=2.3.1"
  • tensorflow-cpu (PyPI): upgrade to 1.15.4, 2.3.1 or later
    pip install "tensorflow-cpu>=2.3.1"
  • tensorflow-gpu (PyPI): upgrade to 1.15.4, 2.3.1 or later
    pip install "tensorflow-gpu>=2.3.1"

Affected products

  • tensorflow (PyPI) ECOSYSTEM:introduced=0,fixed=1.15.4, GIT:introduced=0,fixed=0462de5b544ed4731aa2fb23946ac22c01856b80|ECOSYSTEM:introduced=0,fixed=1.15.4,introduced=2.0.0,fixed=2.0.3,introduced=2.1.0,fixed=2.1.2,introduced=2.2.0,fixed=2.2.1,introduced=2.3.0,fixed=2.3.1
  • tensorflow-cpu (PyPI) ECOSYSTEM:introduced=0,fixed=1.15.4, GIT:introduced=0,fixed=0462de5b544ed4731aa2fb23946ac22c01856b80|ECOSYSTEM:introduced=0,fixed=1.15.4,introduced=2.0.0,fixed=2.0.3,introduced=2.1.0,fixed=2.1.2,introduced=2.2.0,fixed=2.2.1,introduced=2.3.0,fixed=2.3.1
  • tensorflow-gpu (PyPI) ECOSYSTEM:introduced=0,fixed=1.15.4, GIT:introduced=0,fixed=0462de5b544ed4731aa2fb23946ac22c01856b80|ECOSYSTEM:introduced=0,fixed=1.15.4,introduced=2.0.0,fixed=2.0.3,introduced=2.1.0,fixed=2.1.2,introduced=2.2.0,fixed=2.2.1,introduced=2.3.0,fixed=2.3.1

Identifiers

  • CVE-2020-15205
  • GHSA-g7p5-5759-qv46
  • PYSEC-2020-128
  • PYSEC-2020-285
  • PYSEC-2020-320

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.