Heap OOB access in unicode ops
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. An attacker can access data outside of bounds of heap allocated array in `tf.raw_ops.UnicodeEncode`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/472c1f12ad9063405737679d4f6bd43094e1d36d/tensorflow/core/kernels/unicode_ops.cc) assumes that the `input_value`/`input_splits` pair specify a valid sparse tensor. 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
`tf.raw_ops.UnicodeEncode` can read outside a heap-allocated array because it assumes `input_value` and `input_splits` describe a valid sparse tensor. An attacker can trigger the read by supplying an invalid pair. The input does not specify whether network access, authentication, or user interaction is required.
Anyone running affected PyPI versions of tensorflow, tensorflow-cpu, or tensorflow-gpu: versions below 2.1.4, 2.2.0–2.2.2, 2.3.0–2.3.2, or 2.4.0–2.4.1.