Missing validation causes denial of service via `GetSessionTensor` 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.GetSessionTensor` does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. 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.GetSessionTensor does not fully validate its input arguments. An attacker who can supply inputs to this operation can trigger a CHECK failure and cause a denial of service. The input does not specify whether network access, authentication, or user interaction is required.
Engineers running PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu versions below 2.6.4, 2.7.0 through 2.7.1, or 2.8.0 should check their installations.