CVE-2020-15202
No exploitation reported by the sources we read.
- Published2020-09-25
- Fixed in2.3.1 · 2.2.1 · 2.1.2 · 2.0.3 · 1.15.4
- WeaknessCWE-197 · CWE-754
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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
dates in UTC- 2020-09-2519:15CVE publishedNVD
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.3 | ≥ 2.3.0, < 2.3.1 | 2.3.1 | NVD · OSV |
| 2.2 | ≥ 2.2.0, < 2.2.1 | 2.2.1 | NVD · OSV |
| 2.1 | ≥ 2.1.0, < 2.1.2 | 2.1.2 | NVD · OSV |
| 2.0 | ≥ 2.0.0, < 2.0.3 | 2.0.3 | NVD · OSV |
| 1.15 | < 1.15.4 | 1.15.4 | NVD · OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 15.2 | = 15.2 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- tensorflow2openSUSE:Leap 15.2all versions · fixed in 2.1.2-lp152.7.3.1and 3 other packages
Fix
- Update Google tensorflow to 2.3.1 · 2.2.1 · 2.1.2 · 2.0.3 · 1.15.4
Advisories and patches
- github.comPatch
- github.comPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- CNACVSS 3.19known since 2026-10-23
- NVDCVSS 3.19read 2026-10-23
- NVDCVSS 2.06.8read 2026-10-23
- CNAweakness (CWE)CWE-197, CWE-754known since 2026-10-23
- FIRST EPSSEPSS score1.3 %2026-11-18
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2020-09-25
Identifiers
- BIT-tensorflow-2020-15202same flawBitnami · Apache-2.0
- EUVD-2020-0198same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-h6fg-mjxg-hqq4same flawGitHub Advisory Database · CC-BY-4.0
- PYSEC-2020-125same flawPyPA Advisory Database · CC-BY-4.0
- PYSEC-2020-282same flawPyPA Advisory Database · CC-BY-4.0
- PYSEC-2020-317same flawPyPA Advisory Database · CC-BY-4.0
- openSUSE-SU-2020:1766-1advisory covering several CVEsopenSUSE · LicenseRef-unstated
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
- Published
- 2020-09-25
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-h6fg-mjxg-hqq4
Frequently asked questions
What is CVE-2020-15202?
Is CVE-2020-15202 actively exploited?
What is the CVSS score for CVE-2020-15202?
Running tensorflow? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-h6fg-mjxg-hqq4
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served