CVE-2020-15204

Segfault in Tensorflow

MEDIUM

5.3

CVSS Score

Published: September 25, 2020 at 06:46 PM UTC

Updated: June 17, 2026 at 02:56 AM UTC

3 products affected across 3 vendorsLeapTensorflowTensorFlow

Using tensorflow by tensorflow?

Get instant alerts when new vulnerabilities affect tensorflow - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.3

Exploit prediction

EPSS 0.9%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Tensorflow · Google

95%

v < 1.15.42.0.0 ≤ v < 2.0.32.1.0 ≤ v < 2.1.22.2.0 ≤ v < 2.2.12.3.0 ≤ v < 2.3.1

Affected range stops below 1.15.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.0.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.1.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.2.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.3.1, so it looks safe — our inference, not a vendor statement

Leap · openSUSEdrupal

95%

15.2

TensorFlow · Tensorflow

60%

v < 1.15.4v < 2.0.3v < 2.1.2v < 2.2.1v < 2.3.1

Affected range stops below 1.15.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.0.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.1.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.2.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.3.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (4)

Vendor Advisoryx_refsource_SUSEMailing ListThird Party Advisory

Source: [email protected]

http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html

x_refsource_MISCPatchThird Party Advisory

Source: [email protected]

https://github.com/tensorflow/tensorflow/commit/9a133d73ae4b4664d22bd1aa6d654fec13c52ee1

x_refsource_MISCThird Party Advisory

Source: [email protected]

https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1

x_refsource_CONFIRMExploitThird Party Advisory

Source: [email protected]

https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q8gv-q7wr-9jf8

CVSS

5.3MEDIUMGitHub_M

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: NONE
Integrity: NONE
Availability: LOW

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card