<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 18 Oct 2026 02:12:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-29571 — Memory corruption in `DrawBoundingBoxesV2`</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-29571</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; tensorflow&lt;/p&gt;
&lt;p&gt;TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs. The implementation(https://github.com/tensorflow/tensorflow/blob/31bd5026304677faa8a0b77602c6154171b9aec1/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L116-L130) assumes that the last element of `boxes` input is 4, as required by [the op](https://www.tensorflow.org/api_docs/python/tf/raw_ops/DrawBoundingBoxesV2). Since this is not checked attackers passing values less than 4 can write outside of bounds of heap allocated objects and cause memory corruption. If the last dimension in `boxes` is less than 4, accesses similar to `tboxes(b, bb, 3)` will access data outside of bounds. Further during code execution there are also writes to these indices. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; tensorflow&lt;/p&gt;
&lt;p&gt;TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs. The implementation(https://github.com/tensorflow/tensorflow/blob/31bd5026304677faa8a0b77602c6154171b9aec1/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L116-L130) assumes that the last element of `boxes` input is 4, as required by [the op](https://www.tensorflow.org/api_docs/python/tf/raw_ops/DrawBoundingBoxesV2). Since this is not checked attackers passing values less than 4 can write outside of bounds of heap allocated objects and cause memory corruption. If the last dimension in `boxes` is less than 4, accesses similar to `tboxes(b, bb, 3)` will access data outside of bounds. Further during code execution there are also writes to these indices. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-29571</guid>
    </item>
    <item>
      <title>GHSA-whr9-vfh2-7hm6 — Memory corruption in `DrawBoundingBoxesV2`</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-whr9-vfh2-7hm6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: tensorflow, PyPI: tensorflow-cpu, PyPI: tensorflow-gpu&lt;/p&gt;
&lt;p&gt;### Impact
The implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs:&lt;/p&gt;
&lt;p&gt;```python
import tensorflow as tf&lt;/p&gt;
&lt;p&gt;images = tf.fill([10, 96, 0, 1], 0.)
boxes = tf.fill([10, 53, 0], 0.)
colors = tf.fill([0, 1], 0.)&lt;/p&gt;
&lt;p&gt;tf.raw_ops.DrawBoundingBoxesV2(images=images, boxes=boxes, colors=colors)
```&lt;/p&gt;
&lt;p&gt;The [implementation](https://github.com/tensorflow/tensorflow/blob/31bd5026304677faa8a0b77602c6154171b9aec1/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L116-L130) assumes that the last element of `boxes` input is 4, as required by [the op](https://www.tensorflow.org/api_docs/python/tf/raw_ops/DrawBoundingBoxesV2). Since this is not checked attackers passing values less than 4 can write outside of bounds of heap allocated objects and cause memory corruption:&lt;/p&gt;
&lt;p&gt;```cc 
const auto tboxes = boxes.tensor&amp;lt;T, 3&amp;gt;();
for (int64 bb = 0; bb &amp;lt; num_boxes; ++bb) {
  ...
  const int64 min_box_row = static_cast&amp;lt;float&amp;gt;(tboxes(b, bb, 0)) * (height - 1);
  const int64 max_box_row = static_cast&amp;lt;float&amp;gt;(tboxes(b, bb, 2)) * (height - 1);
  const int64 min_box_col = static_cast&amp;lt;float&amp;gt;(tboxes(b, bb, 1)) * (width - 1);
  const int64 max_box_col = static_cast&amp;lt;float&amp;gt;(tboxes(b, bb, 3)) * (width - 1);
  ...
}
```&lt;/p&gt;
&lt;p&gt;If the last dimension in `boxes` is less than 4, accesses similar to `tboxes(b, bb, 3)` will access data outside of bounds. Further during code execution there are also writes to these indices.&lt;/p&gt;
&lt;p&gt;### Patche…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: tensorflow, PyPI: tensorflow-cpu, PyPI: tensorflow-gpu&lt;/p&gt;
&lt;p&gt;### Impact
The implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs:&lt;/p&gt;
&lt;p&gt;```python
import tensorflow as tf&lt;/p&gt;
&lt;p&gt;images = tf.fill([10, 96, 0, 1], 0.)
boxes = tf.fill([10, 53, 0], 0.)
colors = tf.fill([0, 1], 0.)&lt;/p&gt;
&lt;p&gt;tf.raw_ops.DrawBoundingBoxesV2(images=images, boxes=boxes, colors=colors)
```&lt;/p&gt;
&lt;p&gt;The [implementation](https://github.com/tensorflow/tensorflow/blob/31bd5026304677faa8a0b77602c6154171b9aec1/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L116-L130) assumes that the last element of `boxes` input is 4, as required by [the op](https://www.tensorflow.org/api_docs/python/tf/raw_ops/DrawBoundingBoxesV2). Since this is not checked attackers passing values less than 4 can write outside of bounds of heap allocated objects and cause memory corruption:&lt;/p&gt;
&lt;p&gt;```cc 
const auto tboxes = boxes.tensor&amp;lt;T, 3&amp;gt;();
for (int64 bb = 0; bb &amp;lt; num_boxes; ++bb) {
  ...
  const int64 min_box_row = static_cast&amp;lt;float&amp;gt;(tboxes(b, bb, 0)) * (height - 1);
  const int64 max_box_row = static_cast&amp;lt;float&amp;gt;(tboxes(b, bb, 2)) * (height - 1);
  const int64 min_box_col = static_cast&amp;lt;float&amp;gt;(tboxes(b, bb, 1)) * (width - 1);
  const int64 max_box_col = static_cast&amp;lt;float&amp;gt;(tboxes(b, bb, 3)) * (width - 1);
  ...
}
```&lt;/p&gt;
&lt;p&gt;If the last dimension in `boxes` is less than 4, accesses similar to `tboxes(b, bb, 3)` will access data outside of bounds. Further during code execution there are also writes to these indices.&lt;/p&gt;
&lt;p&gt;### Patche…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-whr9-vfh2-7hm6</guid>
    </item>
  </channel>
</rss>
