`CHECK`-failures during Grappler's `SafeToRemoveIdentity` 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.6.0 · < 2.6.3≥ 2.7.0 · < 2.7.1
|
| tensorflow-gpu PyPI |
|
|
Tensorflow is an Open Source Machine Learning Framework. The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a `SavedModel` such that `SafeToRemoveIdentity` would trigger `CHECK` failures. 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
The Grappler optimizer can trigger a CHECK failure when it processes an altered SavedModel, causing a denial of service. An attacker would need to get the affected TensorFlow installation to process that model; the input does not specify network access, authentication requirements, or user interaction.
Teams running PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu versions below 2.5.3, from 2.6.0 to below 2.6.3, or from 2.7.0 to below 2.7.1 should check their installations.