Type confusion leading to `CHECK`-failure based denial of service 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.7.0 · < 2.7.2≥ 2.8.0 · < 2.8.1
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the macros that TensorFlow uses for writing assertions (e.g., `CHECK_LT`, `CHECK_GT`, etc.) have an incorrect logic when comparing `size_t` and `int` values. Due to type conversion rules, several of the macros would trigger incorrectly. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.
From the CVE record · GitHub_M
TensorFlow assertion macros can behave incorrectly when comparing `size_t` and `int` values because of type conversion rules. This can cause assertions to trigger incorrectly. The input does not specify an attacker action, access requirement, or user interaction.
Engineers using the PyPI packages tensorflow, tensorflow-cpu, or tensorflow-gpu in versions below 2.6.4, from 2.7.0 to below 2.7.2, or from 2.8.0 to below 2.8.1 should check their installations.