ThreadUnsafeUnigramCandidateSampler Heap out of bounds in Tensorflow
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
< 2.8.4≥ 2.9.0 · < 2.9.3
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an open source platform for machine learning. When the `BaseCandidateSamplerOp` function receives a value in `true_classes` larger than `range_max`, a heap oob read occurs. We have patched the issue in GitHub commit b389f5c944cadfdfe599b3f1e4026e036f30d2d4. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range.
From the CVE record · GitHub_M
TensorFlow’s BaseCandidateSamplerOp can read beyond heap bounds when true_classes contains a value greater than range_max. An attacker who can supply such a value could trigger the read; the input does not specify network access, authentication requirements, or user interaction.
Teams using the PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu packages should check installations below 2.8.4, from 2.9.0 to before 2.9.3, or from 2.10.0 to before 2.10.1.