MISFIRE

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

Reference binding to nullptr in map operations

CVE-2021-37671 ยท 2021-08-25 high

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:H/I:H/A:H
EPSS
0.2% chance of exploitation in 30 days

How it works, in short

An empty indices argument in map operations leaves a reference bound to null, causing undefined behaviour in the kernel. (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.Map* and tf.raw_ops.OrderedMap* operations:

import tensorflow as tf
  
tf.raw_ops.MapPeek(
  key=tf.constant([8],dtype=tf.int64),
  indices=[],
  dtypes=[tf.int32],
  capacity=8,
  memory_limit=128)

The implementation has a check in place to ensure that indices is in ascending order, but does not check that indices is not empty.

### Patches
We have patched the issue in GitHub commit 532f5c5a547126c634fefd43bbad1dc6417678ac.

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.