`CHECK`-failures in Tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
≥ 2.6.0 · < 2.6.3≥ 2.7.0 · < 2.7.1
|
| tensorflow-gpu PyPI |
|
|
Tensorflow is an Open Source Machine Learning Framework. The implementation of `MapStage` is vulnerable a `CHECK`-fail if the key tensor is not a scalar. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
From the CVE record · GitHub_M
TensorFlow’s MapStage implementation fails a CHECK when the key tensor is not a scalar. An attacker who can cause MapStage to receive such a tensor can trigger the failure; the input does not specify network access, authentication, or user-interaction requirements.
Check deployments using the PyPI packages tensorflow, tensorflow-cpu, or tensorflow-gpu in versions below 2.5.3, from 2.6.0 to below 2.6.3, or from 2.7.0 to below 2.7.1.