CVE-2020-15205
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.
- Affected products
- Suse, Tensorflow
- Google Tensorflow
- < 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1
- Fix
- Available
- CVSS 3.1
- 9.8 CRITICAL
- EPSS
- 1.0% (60th percentile)
- Weakness
- CWE-787, CWE-119, CWE-122
- NVD status
- Modified
- Published
- 2020-09-25
No indexed exploits for CVE-2020-15205 yet
Our index is partial: it proves presence, never absence
No exploit for CVE-2020-15205 has been indexed yet. Our index is built from live traffic and upstream syncs, so this page can only say what it knows — not that no exploit exists.