Data leak in Tensorflow
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
2.3.1| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
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.
From the CVE record · GitHub_M
The `data_splits` argument of `tf.raw_ops.StringNGrams` lacks validation in affected TensorFlow versions. A user who can supply crafted values can cause a heap overflow and leak memory contents, potentially defeating ASLR. The input does not specify network access, authentication requirements, or user interaction.
Anyone running affected versions of the PyPI packages tensorflow, tensorflow-cpu, or tensorflow-gpu before 1.15.4, or in the 2.0–2.3 release lines before 2.0.3, 2.1.2, 2.2.1, or 2.3.1, respectively, should check their installation.