MISFIRE

Browse / AI Framework and Platform Flaws / CVE-2022-21739

Null pointer dereference in TensorFlow

CVE-2022-21739 ยท 2022-02-09 high

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

How it works, in short

A crafted raw-op call with an empty min_input tensor makes the quantized max pool kernel bind a reference to a null pointer. (Our summary, written by a model. The source text is below.)

Details

Impact

The implementation of QuantizedMaxPool has an undefined behavior where user controlled inputs can trigger a reference binding to null pointer.

import tensorflow as tf

tf.raw_ops.QuantizedMaxPool(
    input = tf.constant([[[[4]]]], dtype=tf.quint8),
    min_input = [],
    max_input = [1],
    ksize = [1, 1, 1, 1],
    strides = [1, 1, 1, 1],
    padding = "SAME", name=None
)

Patches

We have patched the issue in GitHub commit 53b0dd6dc5957652f35964af16b892ec9af4a559.

The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, 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 Faysal Hossain Shezan from University of Virginia.

References

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