`CHECK` fail in `RaggedTensorToVariant` 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 `RaggedTensorToVariant` is given a `rt_nested_splits` list that contains tensors of ranks other than one, 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 88f93dfe691563baa4ae1e80ccde2d5c7a143821. 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
RaggedTensorToVariant fails a CHECK when its rt_nested_splits list contains tensors with ranks other than one. An attacker who can supply such input can trigger a denial of service; the input does not specify network access, authentication, or user-interaction requirements.
Anyone running 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 should check their installations.