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.
References
Link | Resource |
---|---|
http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html | Mailing List Third Party Advisory |
https://github.com/tensorflow/tensorflow/commit/0462de5b544ed4731aa2fb23946ac22c01856b80 | Patch Third Party Advisory |
https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1 | Third Party Advisory |
https://github.com/tensorflow/tensorflow/security/advisories/GHSA-g7p5-5759-qv46 | Exploit Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: GitHub_M
Published: 2020-09-25T18:45:57
Updated: 2020-10-29T15:06:23
Reserved: 2020-06-25T00:00:00
Link: CVE-2020-15205
JSON object: View
NVD Information
Status : Analyzed
Published: 2020-09-25T19:15:15.823
Modified: 2021-11-18T17:27:14.957
Link: CVE-2020-15205
JSON object: View
Redhat Information
No data.