CVE-2021-29529 Heap buffer overflow caused by rounding

What is CVE-2021-29529?

CVE-2021-29529 is a low-severity memory corruption vulnerability in Google Tensorflow, published on 14 May 2021. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a heap buffer overflow in `tf.raw_ops.QuantizedResizeBilinear` by manipulating input values so that float rounding results in off-by-one error in accessing image elements. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/44b7f486c0143f68b56c34e2d01e146ee445134a/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L62-L66) computes two integers (representing the upper and lower bounds for interpolation) by ceiling and flooring a floating point value. For some values of `in`, `interpolation->upper[i]` might be smaller than `interpolation->lower[i]`. This is an issue if `interpolation->upper[i]` is capped at `in_size-1` as it means that `interpolation->lower[i]` points outside of the image. Then, in the interpolation code(https://github.com/tensorflow/tensorflow/blob/44b7f486c0143f68b56c34e2d01e146ee445134a/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L245-L264), this would result in heap buffer overflow. 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.

Weakness: CWE-193, CWE-131

Which versions are affected by CVE-2021-29529?

28 open source packages ship an affected version, including tensorflow, tensorflow-cpu and tensorflow-gpu. It affects 1 product.

Products include Google Tensorflow.

How do I fix CVE-2021-29529?

Upgrade tensorflow to a fixed version for your release line: 2.1.4, 2.2.3, 2.3.3 or 2.4.2.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2021-29529 being exploited?

There is no known exploitation of CVE-2021-29529 in the wild and no public exploit code.

Other vulnerabilities in Google Tensorflow

• CVE-2023-25668 TensorFlow vulnerable to heap out-of-buffer read in the QuantizeAndDequantize operation Critical 9.8
• CVE-2018-7575 Integer Overflow or Wraparound in Google TensorFlow Critical 9.8
• CVE-2021-37678 Arbitrary code execution due to YAML deserialization Critical 9.3
• CVE-2021-35958 Path traversal in n/a Critical 9.1
• CVE-2020-15202 Integer truncation in Shard API usage Critical 9.0

All Google Tensorflow vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as BIT-tensorflow-2021-29529, GHSA-jfp7-4j67-8r3q, PYSEC-2021-166, PYSEC-2021-457, PYSEC-2021-655.