Heap OOB and null pointer dereference in `RaggedTensorToTensor`
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. Due to lack of validation in `tf.raw_ops.RaggedTensorToTensor`, an attacker can exploit an undefined behavior if input arguments are empty. The implementation(https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L356-L360) only checks that one of the tensors is not empty, but does not check for the other ones. There are multiple `DCHECK` validations to prevent heap OOB, but these are no-op in release builds, hence they don't prevent anything. The fix will be included in TensorFlow 2.5.0. We will also cherrypick these commits 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
`tf.raw_ops.RaggedTensorToTensor` does not fully validate empty input tensors, and its heap out-of-bounds checks are inactive in release builds. An attacker who can supply empty input arguments can trigger undefined behavior; the input does not specify whether this requires network or local access, authentication, or user interaction.
Engineers using the affected versions of the PyPI packages tensorflow, tensorflow-cpu, or tensorflow-gpu should check their deployments.