`CHECK` fail in `Save` and `SaveSlices` 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.8.0 · < 2.8.1≥ 2.9.0 · < 2.9.1
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an open source platform for machine learning. If `Save` or `SaveSlices` is run over tensors of an unsupported `dtype`, it results in a `CHECK` fail that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 5dd7b86b84a864b834c6fa3d7f9f51c87efa99d4. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue.
From the CVE record · GitHub_M
Running Save or SaveSlices on tensors with an unsupported dtype causes a CHECK failure. An attacker who can cause either operation to run on such a tensor can trigger 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.7.2, from 2.8.0 to below 2.8.1, or from 2.9.0 to below 2.9.1.