`CHECK` fail in `LRNGrad` 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 `LRNGrad` is given an `output_image` input tensor that is not 4-D, 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 bd90b3efab4ec958b228cd7cfe9125be1c0cf255. 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
TensorFlow's LRNGrad fails a CHECK when its output_image input tensor is not 4-D. An attacker who can cause LRNGrad to process such a tensor can trigger a denial of service. The input does not specify network access, authentication, or user-interaction requirements.
Teams 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.