https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 05:51:49 +0000 https://cve.radiocsirt.org/vuln/bit-tensorflow-2020-15205 <p><strong>Affected:</strong> Bitnami: tensorflow</p> <p>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.</p> <p><strong>Affected:</strong> Bitnami: tensorflow</p> <p>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.</p> https://cve.radiocsirt.org/vuln/bit-tensorflow-2020-15205 https://cve.radiocsirt.org/vuln/cnvd-2020-54474 cnvd-2020-54474 https://cve.radiocsirt.org/vuln/cnvd-2020-54474 https://cve.radiocsirt.org/vuln/euvd-2026-42732 EUVD-2026-42732 https://cve.radiocsirt.org/vuln/euvd-2026-42732 https://cve.radiocsirt.org/vuln/fkie_cve-2020-15205 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-15205 https://cve.radiocsirt.org/vuln/ghsa-g7p5-5759-qv46 <p><strong>Affected:</strong> PyPI: tensorflow, PyPI: tensorflow-cpu, PyPI: tensorflow-gpu</p> <p>### Impact The `data_splits` argument of [`tf.raw_ops.StringNGrams`](https://www.tensorflow.org/api_docs/python/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 ```python &gt;&gt;&gt; tf.raw_ops.StringNGrams(data=[&#34;aa&#34;, &#34;bb&#34;, &#34;cc&#34;, &#34;dd&#34;, &#34;ee&#34;, &#34;ff&#34;], data_splits=[0,8], separator=&#34; &#34;, ngram_widths=[3], left_pad=&#34;&#34;, right_pad=&#34;&#34;, pad_width=0, preserve_short_sequences=False) StringNGrams(ngrams=&lt;tf.Tensor: shape=(6,), dtype=string, numpy= array([b&#39;aa bb cc&#39;, b&#39;bb cc dd&#39;, b&#39;cc dd ee&#39;, b&#39;dd ee ff&#39;, b&#39;ee ff \xf4j\xa7q\x7f\x00\x00q\x00\x00\x00\x00\x00\x00\x00\xd8\x9b~\xa8q\x7f\x00&#39;, b&#39;ff \xf4j\xa7q\x7f\x00\x00q\x00\x00\x00\x00\x00\x00\x00\xd8\x9b~\xa8q\x7f\x00 \x9b~\xa8q\x7f\x00\x00p\xf5j\xa7q\x7f\x00\x00H\xf8j\xa7q\x7f\x00\x00\xf0\xf3\xf7\x85q\x7f\x00\x00`}\xa6\x00\x00\x00\x00\x00`~\xa6\x00\x00\x00\x00\x00\xb0~\xeb\x9bq\x7f\x00&#39;],... ```</p> <p>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.</p> <p>### Patches We have patched the issue in 0462de5b544ed4731aa2fb23946ac22c01856b80 and will release patch releases for all versions between 1.15 and 2.3.</p> <p>We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.</p> <p>### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regardi…</p> <p><strong>Affected:</strong> PyPI: tensorflow, PyPI: tensorflow-cpu, PyPI: tensorflow-gpu</p> <p>### Impact The `data_splits` argument of [`tf.raw_ops.StringNGrams`](https://www.tensorflow.org/api_docs/python/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 ```python &gt;&gt;&gt; tf.raw_ops.StringNGrams(data=[&#34;aa&#34;, &#34;bb&#34;, &#34;cc&#34;, &#34;dd&#34;, &#34;ee&#34;, &#34;ff&#34;], data_splits=[0,8], separator=&#34; &#34;, ngram_widths=[3], left_pad=&#34;&#34;, right_pad=&#34;&#34;, pad_width=0, preserve_short_sequences=False) StringNGrams(ngrams=&lt;tf.Tensor: shape=(6,), dtype=string, numpy= array([b&#39;aa bb cc&#39;, b&#39;bb cc dd&#39;, b&#39;cc dd ee&#39;, b&#39;dd ee ff&#39;, b&#39;ee ff \xf4j\xa7q\x7f\x00\x00q\x00\x00\x00\x00\x00\x00\x00\xd8\x9b~\xa8q\x7f\x00&#39;, b&#39;ff \xf4j\xa7q\x7f\x00\x00q\x00\x00\x00\x00\x00\x00\x00\xd8\x9b~\xa8q\x7f\x00 \x9b~\xa8q\x7f\x00\x00p\xf5j\xa7q\x7f\x00\x00H\xf8j\xa7q\x7f\x00\x00\xf0\xf3\xf7\x85q\x7f\x00\x00`}\xa6\x00\x00\x00\x00\x00`~\xa6\x00\x00\x00\x00\x00\xb0~\xeb\x9bq\x7f\x00&#39;],... ```</p> <p>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.</p> <p>### Patches We have patched the issue in 0462de5b544ed4731aa2fb23946ac22c01856b80 and will release patch releases for all versions between 1.15 and 2.3.</p> <p>We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.</p> <p>### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regardi…</p> https://cve.radiocsirt.org/vuln/ghsa-g7p5-5759-qv46 https://cve.radiocsirt.org/vuln/gsd-2020-15205 gsd-2020-15205 https://cve.radiocsirt.org/vuln/gsd-2020-15205 https://cve.radiocsirt.org/vuln/opensuse-su-2020:1766-1 <p>Security update for tensorflow2</p> <p>Security update for tensorflow2</p> https://cve.radiocsirt.org/vuln/opensuse-su-2020:1766-1 https://cve.radiocsirt.org/vuln/pysec-2020-128 <p><strong>Affected:</strong> PyPI: tensorflow</p> <p>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.</p> <p><strong>Affected:</strong> PyPI: tensorflow</p> <p>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.</p> https://cve.radiocsirt.org/vuln/pysec-2020-128