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 tensor from protobuf, a TensorFlow process can encounter cases where a `CHECK` assertion is invalidated based on user controlled arguments, if the tensors have an invalid `dtype` and 0 elements or an invalid shape. 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 fail a CHECK assertion while decoding a protobuf tensor with an invalid dtype and zero elements, or an invalid shape. An attacker who can supply such a tensor can cause a TensorFlow process to stop. The input does not specify whether network access, authentication, or user interaction is required.
Check PyPI installations of tensorflow, tensorflow-cpu, or tensorflow-gpu at versions below 2.5.3, from 2.6.0 to below 2.6.3, or from 2.7.0 to below 2.7.1.