Skip to main content
No exploitation reportedFix available

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?

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
  1. 2020-09-2519:15CVE publishedNVD

Versions per branch

NVD · OSV
Google tensorflow
BranchAffectedFixed in
2.3≥ 2.3.0, < 2.3.12.3.1
2.2≥ 2.2.0, < 2.2.12.2.1
2.1≥ 2.1.0, < 2.1.22.1.2
2.0≥ 2.0.0, < 2.0.32.0.3
1.15< 1.15.41.15.4
Opensuse leap
BranchAffectedFixed in
15.2= 15.2no fix published

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

Full record on NVD

Fix

  1. Update Google tensorflow to 2.3.1 · 2.2.1 · 2.1.2 · 2.0.3 · 1.15.4

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
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

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?

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.

Is CVE-2020-15205 actively exploited?

Active exploitation of CVE-2020-15205 has not been confirmed. Its EPSS score was 1.0% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-15205?

CVE-2020-15205 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

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

Sources for this record