Segfault and Out-of-bounds Write write due to incomplete validation 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.7.0 · < 2.7.2≥ 2.8.0 · < 2.8.1
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.EditDistance` has incomplete validation. Users can pass negative values to cause a segmentation fault based denial of service. In multiple places throughout the code, one may compute an index for a write operation. However, the existing validation only checks against the upper bound of the array. Hence, it is possible to write before the array by massaging the input to generate negative values for `loc`. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.
From the CVE record · GitHub_M
Incomplete validation in tf.raw_ops.EditDistance allows negative input values to cause a segmentation fault and denial of service. The input can also produce a write before an array. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Check deployments using affected PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu versions below 2.6.4, from 2.7.0 to below 2.7.2, or from 2.8.0 to below 2.8.1.