critical

CVE-2020-15202

Integer truncation in Shard API usage

Published 25 Sep 2020Modified 17 Jun 2026CWE 197, 754

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.0CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

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

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

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

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.

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 10 references

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