vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2020-15202

Integer truncation in Shard API usage

CRITICAL
9
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 FreeSign In
Severity
CRITICAL9
Exploit prediction
EPSS 1%

Description

In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `Shard` API in TensorFlow expects the last argument to be a function taking two `int64` (i.e., `long long`) arguments. However, there are several places in TensorFlow where a lambda taking `int` or `int32` arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption. The issue is patched in commits 27b417360cbd671ef55915e4bb6bb06af8b8a832 and ca8c013b5e97b1373b3bb1c97ea655e69f31a575, 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

References (5)

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/27b417360cbd671ef55915e4bb6bb06af8b8a832
x_refsource_MISCPatchThird Party Advisory
Source: [email protected]
https://github.com/tensorflow/tensorflow/commit/ca8c013b5e97b1373b3bb1c97ea655e69f31a575
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-h6fg-mjxg-hqq4

CVSS

9CRITICALGitHub_M
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-197CWE-754NVD-CWE-Other

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 accountSign in
Free plan, no card