CVE-2020-15205
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.
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.