Segfault in `QuantizedAdd` 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 `QuantizedAdd` is given `min_input` or `max_input` tensors of a nonzero rank, it results in a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 49b3824d83af706df0ad07e4e677d88659756d89. 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 QuantizedAdd operation can segfault if its min_input or max_input tensor has nonzero rank. An attacker who can cause the operation to receive such a tensor can trigger a denial of service; the input does not specify network access, authentication, or user-interaction requirements.
Teams running affected PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu versions below 2.7.2, from 2.8.0 to before 2.8.1, or from 2.9.0 to before 2.9.1 should check their installations.