MISFIRE

Browse / AI Framework and Platform Flaws / CVE-2021-37656

Reference binding to nullptr in `RaggedTensorToSparse`

CVE-2021-37656 ยท 2021-08-25 moderate

Class
AI Framework and Platform Flaws (filed by a model that read the source)
Technique
Memory corruption
Affected
tensorflow-cpu, tensorflow (PyPI)
CVSS
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS
0.2% chance of exploitation in 30 days

How it works, in short

A ragged-tensor op accepts a splits array without checking ordering, binding a reference to null and causing undefined behaviour. (Our summary, written by a model. The source text is below.)

Details

Impact

An attacker can cause undefined behavior via binding a reference to null pointer in tf.raw_ops.RaggedTensorToSparse:

import tensorflow as tf

tf.raw_ops.RaggedTensorToSparse(
  rt_nested_splits=[[0, 38, 0]],
  rt_dense_values=[])

The implementation has an incomplete validation of the splits values: it does not check that they are in increasing order.

Patches

We have patched the issue in GitHub commit 1071f554dbd09f7e101324d366eec5f4fe5a3ece.

The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution

This vulnerability has been reported by members of the Aivul Team from Qihoo 360.

References

Source: GitHub Advisory Database, used under CC BY 4.0.