Missing validation causes denial of service in TensorFlow via `StagePeek`
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.StagePeek` does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. The code assumes `index` is a scalar but there is no validation for this before accessing its value. 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
TensorFlow's tf.raw_ops.StagePeek does not validate that its index argument is a scalar. An attacker who can supply a non-scalar index to this operation can trigger a CHECK failure and cause a denial of service. The input does not specify network access, authentication, or user-interaction requirements.
Check deployments using 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.