CHECK-fail in SparseCross due to type confusion
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an end-to-end open source platform for machine learning. The API of `tf.raw_ops.SparseCross` allows combinations which would result in a `CHECK`-failure and denial of service. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/3d782b7d47b1bf2ed32bd4a246d6d6cadc4c903d/tensorflow/core/kernels/sparse_cross_op.cc#L114-L116) is tricked to consider a tensor of type `tstring` which in fact contains integral elements. Fixing the type confusion by preventing mixing `DT_STRING` and `DT_INT64` types solves this issue. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
From the CVE record · GitHub_M
The `tf.raw_ops.SparseCross` API has a type confusion flaw when `DT_STRING` and `DT_INT64` inputs are mixed. An attacker who can supply such inputs can trigger a `CHECK` failure and cause a denial of service. The input does not specify network access, authentication requirements, or user interaction.
Engineers running the PyPI packages `tensorflow`, `tensorflow-cpu`, or `tensorflow-gpu` should check for versions below 2.1.4, 2.2.0–2.2.2, 2.3.0–2.3.2, or 2.4.0–2.4.1.