CVE-2020-15205
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-119 · CWE-122 · CWE-787
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 `data_splits` argument of `tf.raw_ops.StringNGrams` lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after `ee ff` are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR. The issue is patched in commit 0462de5b544ed4731aa2fb23946ac22c01856b80, 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
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.19.8read 2026-10-23
- NVDCVSS 2.07.5read 2026-10-23
- CNAweakness (CWE)CWE-119, CWE-122known since 2026-10-23
- NVDweakness (CWE)CWE-787read 2026-10-23
- FIRST EPSSEPSS score1.0 %2026-11-18
- OSVaffected packages—
- GitHub AdvisoriesadvisoryMODERATE2020-09-25
Identifiers
- BIT-tensorflow-2020-15205same flawBitnami · Apache-2.0
- EUVD-2020-0201same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-g7p5-5759-qv46same flawGitHub Advisory Database · CC-BY-4.0
- PYSEC-2020-128same flawPyPA Advisory Database · CC-BY-4.0
- PYSEC-2020-285same flawPyPA Advisory Database · CC-BY-4.0
- PYSEC-2020-320same 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:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2020-09-25
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-g7p5-5759-qv46
Frequently asked questions
What is CVE-2020-15205?
Is CVE-2020-15205 actively exploited?
What is the CVSS score for CVE-2020-15205?
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-g7p5-5759-qv46
- 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