CVE-2020-15202
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.
How to fix
- google tensorflow1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1 or later
- tensorflow1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1 or later
- tensorflow-cpu1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1 or later
- tensorflow-gpu1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| google tensorflow | v < 1.15.4, 2.0.0 ≤ v < 2.0.3, 2.1.0 ≤ v < 2.1.2, 2.2.0 ≤ v < 2.2.1, 2.3.0 ≤ v < 2.3.1 | 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1 |
| opensuse leap | 15.2 | — |
| tensorflowPyPI | v < 1.15.4, 2.0.0 ≤ v < 2.0.3, 2.1.0 ≤ v < 2.1.2, 2.2.0 ≤ v < 2.2.1, 2.3.0 ≤ v < 2.3.1 | 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1 |
| tensorflow-cpuPyPI | v < 1.15.4, 2.0.0 ≤ v < 2.0.3, 2.1.0 ≤ v < 2.1.2, 2.2.0 ≤ v < 2.2.1, 2.3.0 ≤ v < 2.3.1 | 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1 |
| tensorflow-gpuPyPI | v < 1.15.4, 2.0.0 ≤ v < 2.0.3, 2.1.0 ≤ v < 2.1.2, 2.2.0 ≤ v < 2.2.1, 2.3.0 ≤ v < 2.3.1 | 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.