Null pointer exception in `DeserializeSparse`
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 shape inference code for `DeserializeSparse` can trigger a null pointer dereference. This is because the shape inference function assumes that the `serialize_sparse` tensor is a tensor with positive rank (and having `3` as the last dimension). 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 versions can trigger a null pointer dereference during `DeserializeSparse` shape inference. An attacker who can supply a `serialize_sparse` tensor that violates the expected shape can trigger the issue; 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 versions below 2.4.4, 2.5.0–2.5.1, 2.6.0, and 2.7.0 release candidates.