CVE-2020-15204

Description

In eager mode, TensorFlow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 does not set the session state. Hence, calling `tf.raw_ops.GetSessionHandle` or `tf.raw_ops.GetSessionHandleV2` results in a null pointer dereference In linked snippet, in eager mode, `ctx->session_state()` returns `nullptr`. Since code immediately dereferences this, we get a segmentation fault. The issue is patched in commit 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.

How to fix CVE-2020-15204

To remediate CVE-2020-15204, upgrade the affected package to a fixed version below.

• —upgrade to 1.15.4 or later
• —upgrade to 1.15.4 or later
• —upgrade to 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1 or later
• —upgrade to 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1 or later
• —upgrade to 1.15.4 or later
• —upgrade to 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1 or later
• —upgrade to 1.15.4 or later

Is CVE-2020-15204 being exploited?

Low — EPSS is 0.2%, meaning exploitation activity has not been observed at scale.

Affected packages (7)

• from 0, < 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
• from 0, < 1.15.4
• from 0, < 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1 | from 0, < 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
• from 0, < 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1 | from 0, < 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
• from 0, < 1.15.4
• from 0, < 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1 | from 0, < 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
• from 0, < 1.15.4

CVSS scores

References (9)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2020-15204
• PATCHgithub.com/tensorflow/tensorflow
• WEBlists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html
• WEBgithub.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-284.yaml