CVE-2020-15202Integer truncation in Shard API usage
- 9.0CriticalCVSS base score
- 1.3%Exploitation in 30 daysEPSS · top 29% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By GitHub_M
- 3 months later
· 3 months later
Published
- 4 years later
· 4 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_MCNA (assigner) | 3.1 | Critical9.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Critical9.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 1.3% · top 29% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.0.
Affected products
- affected < 1.15.4
- affected >= 2.0.0, < 2.0.3
- affected >= 2.1.0, < 2.1.2
- affected >= 2.2.0, < 2.2.1
- affected >= 2.3.0, < 2.3.1
Affected packages
From reviewed advisories of the GitHub Advisory Database.
- PyPItensorflowGHSA-h6fg-mjxg-hqq4 (opens in a new tab)
- PyPItensorflow-cpuGHSA-h6fg-mjxg-hqq4 (opens in a new tab)
- PyPItensorflow-gpuGHSA-h6fg-mjxg-hqq4 (opens in a new tab)
References
References5
- https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1 (opens in a new tab)x_refsource_MISCx_transferred
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6fg-mjxg-hqq4 (opens in a new tab)x_refsource_CONFIRMx_transferred
- https://github.com/tensorflow/tensorflow/commit/27b417360cbd671ef55915e4bb6bb06af8b8a832 (opens in a new tab)x_refsource_MISCx_transferred
- https://github.com/tensorflow/tensorflow/commit/ca8c013b5e97b1373b3bb1c97ea655e69f31a575 (opens in a new tab)x_refsource_MISCx_transferred
- openSUSE-SU-2020:1766 (opens in a new tab)vendor-advisoryx_refsource_SUSEx_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2020-0198 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisory GHSA-h6fg-mjxg-hqq4 (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2020-15202)Record last updated .