Integer truncation in Shard API usage
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- tensorflow tensorflow
fixed in 1.15.4; From 2.0.0 · fixed in 2.0.3; From 2.1.0 · fixed in 2.1.2; From 2.2.0 · fixed in 2.2.1; From 2.3.0 · fixed in 2.3.1
- tensorflowPyPI
fixed in 1.15.4; From 2.0.0 · fixed in 2.0.3; From 2.1.0 · fixed in 2.1.2; From 2.2.0 · fixed in 2.2.1; From 2.3.0 · fixed in 2.3.1
- tensorflowPyPI
fixed in 1.15.4
- tensorflowPyPI
From 2.0.0 · fixed in 2.0.3
- tensorflowPyPI
From 2.1.0 · fixed in 2.1.2
- tensorflowPyPI
From 2.2.0 · fixed in 2.2.1
- tensorflowPyPI
From 2.3.0 · fixed in 2.3.1
- tensorflow-cpuPyPI
fixed in 1.15.4
- tensorflow-cpuPyPI
From 2.0.0 · fixed in 2.0.3
- tensorflow-cpuPyPI
From 2.1.0 · fixed in 2.1.2
- tensorflow-cpuPyPI
From 2.2.0 · fixed in 2.2.1
- tensorflow-cpuPyPI
From 2.3.0 · fixed in 2.3.1
- tensorflow-gpuPyPI
fixed in 1.15.4
- tensorflow-gpuPyPI
From 2.0.0 · fixed in 2.0.3
- tensorflow-gpuPyPI
From 2.1.0 · fixed in 2.1.2
- tensorflow-gpuPyPI
From 2.2.0 · fixed in 2.2.1
- tensorflow-gpuPyPI
From 2.3.0 · fixed in 2.3.1
- tensorflow-gpuPyPI
fixed in 1.15.4; From 2.0.0 · fixed in 2.0.3; From 2.1.0 · fixed in 2.1.2; From 2.2.0 · fixed in 2.2.1; From 2.3.0 · fixed in 2.3.1
- tensorflow-cpuPyPI
fixed in 1.15.4; From 2.0.0 · fixed in 2.0.3; From 2.1.0 · fixed in 2.1.2; From 2.2.0 · fixed in 2.2.1; From 2.3.0 · fixed in 2.3.1