Data leak in Tensorflow
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9epss 1.0%
exploitation probability
1.0%top 38% of all CVEs
observed exploitation
nono source reports it
In short
TensorFlow's StringNGrams function doesn't validate user input properly, allowing attackers to read sensitive data from the computer's memory. This can leak information needed to bypass security protections.
Technical detail
The `data_splits` argument in tf.raw_ops.StringNGrams lacks input validation, enabling heap buffer overflow that leaks adjacent memory contents including stack addresses. An attacker can exploit this to extract data for ASLR bypass without requiring elevated privileges.
Summary generated and translated by AI from the official 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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Affected products
tensorflow · tensorflowReferences
http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.htmlhttps://github.com/tensorflow/tensorflow/commit/0462de5b544ed4731aa2fb23946ac22c01856b80https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1https://github.com/tensorflow/tensorflow/security/advisories/GHSA-g7p5-5759-qv46