Heap OOB read in `SparseBinCount`
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an open source platform for machine learning. In affected versions the implementation of `SparseBinCount` is vulnerable to a heap OOB access. This is because of missing validation between the elements of the `values` argument and the shape of the sparse output. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
From the CVE record · GitHub_M
Affected TensorFlow packages have a heap out-of-bounds access in SparseBinCount because they do not validate the values argument against the sparse output shape. The issue can occur when SparseBinCount processes inconsistent values and output shapes. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Users of PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu should check versions earlier than 2.4.4, 2.5.0–2.5.1, 2.6.0, and 2.7.0 release candidates.