critical

CVE-2020-15205

Data leak in Tensorflow

Published 25 Sep 2020Modified 17 Jun 2026CWE 119, 122, 787

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

NVD9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

GHSA6.5CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H

Bitnami9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Trivy's own label is CRITICAL. Rated critical by NVD, Bitnami. Rated lower by GHSA (medium).

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.

Affected packages and fixed versions

Source	Package	Fixed in
bitnami::Bitnami Vulnerability Database	tensorflow	1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1
pip::GitHub Security Advisory pip	tensorflow, tensorflow-cpu, tensorflow-gpu	1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1

Show all 4 entries from 2 sources

Source	Package	Fixed in
bitnami::Bitnami Vulnerability Database	tensorflow	1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1
pip::GitHub Security Advisory pip	tensorflow	1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1
pip::GitHub Security Advisory pip	tensorflow-cpu	1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1
pip::GitHub Security Advisory pip	tensorflow-gpu	1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1

References

All 9 references

https://nvd.nist.gov/vuln/detail/CVE-2020-15205

What Attestkeep does with this

Inside your cluster, without you opening a spreadsheet.

KnowsThe scanner refreshes its vulnerability database every six hours.

FindsEvery admitted image is rescanned every 24 hours by default (scan.rescanInterval). When Trivy rates this vulnerability critical for the image's package source, it appears in the image's findings by name. Findings without a fix are left out unless includeUnfixed is on.

Tells youA critical_finding event goes to the channels subscribed to it: e-mail, Slack, Teams, a webhook, Jira, GitLab or GitHub.

RefusesWith a policy that blocks critical findings, a pod with this image is refused at admission, a rollback to it included. Pods already running are not evicted.

RecordsEach decision is recorded with the policy that ran and its hash, then sealed under a signed checkpoint.

Try Attestkeep

Read the docs