Reachable Assertion 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.6.0 · < 2.6.3≥ 2.7.0 · < 2.7.1
|
| tensorflow-gpu PyPI |
|
|
Tensorflow is an Open Source Machine Learning Framework. When decoding a resource handle tensor from protobuf, a TensorFlow process can encounter cases where a `CHECK` assertion is invalidated based on user controlled arguments. This allows attackers to cause denial of services in TensorFlow processes. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
From the CVE record · GitHub_M
TensorFlow can hit an invalidated CHECK assertion when decoding a resource handle tensor from protobuf. An attacker who controls arguments used in that decoding can cause a TensorFlow process to deny service. The input does not specify network access, authentication requirements, or user interaction.
Check deployments using affected PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu versions: below 2.5.3, 2.6.0 through 2.6.2, or 2.7.0.