Undefined behavior in Tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
≥ 2.6.0 · < 2.6.3≥ 2.7.0 · < 2.7.1
|
| tensorflow-gpu PyPI |
|
|
Tensorflow is an Open Source Machine Learning Framework. The implementation of `SparseTensorSliceDataset` has an undefined behavior: under certain condition it can be made to dereference a `nullptr` value. The 3 input arguments to `SparseTensorSliceDataset` represent a sparse tensor. However, there are some preconditions that these arguments must satisfy but these are not validated in the implementation. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
From the CVE record · GitHub_M
SparseTensorSliceDataset does not validate required preconditions on its three sparse-tensor inputs. An attacker who can supply inputs that violate those preconditions can trigger a null-pointer dereference. The input does not specify network access, authentication requirements, or user interaction.
Engineers using the PyPI packages tensorflow, tensorflow-cpu, or tensorflow-gpu in versions below 2.5.3, from 2.6.0 to below 2.6.3, or from 2.7.0 to below 2.7.1 should check their installations.