CVE-2020-15203

Denial of Service in Tensorflow

HIGH

7.5

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

HIGH7.5

Exploit prediction

EPSS 1.0%

Description

In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, by controlling the `fill` argument of tf.strings.as_string, a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a `printf` call is constructed. This may result in segmentation fault. The issue is patched in commit 33be22c65d86256e6826666662e40dbdfe70ee83, 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/33be22c65d86256e6826666662e40dbdfe70ee83

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-xmq7-7fxm-rr79

CVSS

7.5HIGHGitHub_M

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

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-20CWE-134

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