`CHECK` fail via inputs in `PyFunc` 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.9.0 · < 2.9.3≥ 2.10.0 · < 2.10.1
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an open source platform for machine learning. An input `token` that is not a UTF-8 bytestring will trigger a `CHECK` fail in `tf.raw_ops.PyFunc`. We have patched the issue in GitHub commit 9f03a9d3bafe902c1e6beb105b2f24172f238645. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range.
From the CVE record · GitHub_M
TensorFlow's tf.raw_ops.PyFunc triggers a CHECK failure when its token input is not a UTF-8 bytestring. An attacker who can supply that input can trigger the failure; the input does not specify network or local access, authentication requirements, or user interaction.
Teams running PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu versions below 2.8.4, 2.9.0 through 2.9.2, or 2.10.0 should check their installations.