Null pointer dereference in `EditDistance`
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 end-to-end open source platform for machine learning. An attacker can trigger a null pointer dereference in the implementation of `tf.raw_ops.EditDistance`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/79865b542f9ffdc9caeb255631f7c56f1d4b6517/tensorflow/core/kernels/edit_distance_op.cc#L103-L159) has incomplete validation of the input parameters. 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.
From the CVE record · GitHub_M
TensorFlow's tf.raw_ops.EditDistance incompletely validates its input parameters. An attacker can trigger a null pointer dereference by supplying inputs to this operation. The input does not specify network access, authentication, or user-interaction requirements.
Engineers using PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu versions below 2.1.4, 2.2.0–2.2.2, 2.3.0–2.3.2, or 2.4.0–2.4.1 should check their installations.