CHECK-fail in `CTCGreedyDecoder`
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
2.1.42.2.32.3.32.4.22.2.0rc02.3.0rc02.3.42.4.3| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.CTCGreedyDecoder`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/1615440b17b364b875eb06f43d087381f1460a65/tensorflow/core/kernels/ctc_decoder_ops.cc#L37-L50) has a `CHECK_LT` inserted to validate some invariants. When this condition is false, the program aborts, instead of returning a valid error to the user. This abnormal termination can be weaponized in denial of service attacks. 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
TensorFlow’s tf.raw_ops.CTCGreedyDecoder can abort the program when an input violates an invariant, rather than returning an error. An attacker who can supply input to this operation can trigger a denial of service; the input does not specify network access, authentication requirements, or user interaction.
Engineers using the PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu packages should check installations below the listed fixed versions in the 2.1 through 2.4 release lines.