`CHECK` fail in `QuantizeAndDequantizeV3` 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 `QuantizeAndDequantizeV3` is given a nonscalar `num_bits` input tensor, 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 f3f9cb38ecfe5a8a703f2c4a8fead434ef291713. 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 QuantizeAndDequantizeV3 fails a CHECK when given a nonscalar num_bits input tensor. An attacker who can supply that input can trigger a denial of service. The input does not specify network access, authentication, or user-interaction requirements.
Teams running affected versions of the PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu packages—below 2.7.2, 2.8.0 through 2.8.0, or 2.9.0 through 2.9.0—should check their installations.