Vulnerability · Published May 14, 2021 · Assigned by GitHub_M

CVE-2021-29614Interpreter crash from `tf.io.decode_raw`

High 7.1

In plain English

A high-severity security flaw in tensorflow from tensorflow. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 13% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.1High
Exploit odds (30 days)0.2%top 87.2% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.io.decode_raw` produces incorrect results and crashes the Python interpreter when combining `fixed_length` and wider datatypes. The implementation of the padded version(https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc) is buggy due to a confusion about pointer arithmetic rules. First, the code computes(https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L61) the width of each output element by dividing the `fixed_length` value to the size of the type argument. The `fixed_length` argument is also used to determine the size needed for the output tensor(https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L63-L79). This is followed by reencoding code(https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L85-L94). The erroneous code is the last line above: it is moving the `out_data` pointer by `fixed_length * sizeof(T)` bytes whereas it only copied at most `fixed_length` bytes from the input. This results in parts of the input not being decoded into the output. Furthermore, because the pointer advance is far wider than desired, this quickly leads to writing to outside the bounds of the backing data. This OOB write leads to interpreter crash in the reproducer mentioned here, but more severe attacks can be mounted too, given that this gadget allows writing to periodically placed locations in memory. 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
PyPItensorflow2.3.3GHSA-8pmx-p244-g88h
PyPItensorflow2.4.2GHSA-8pmx-p244-g88h
PyPItensorflow2.1.4GHSA-8pmx-p244-g88h
PyPItensorflow2.1.4, 2.2.3, 2.3.3, 2.4.2PYSEC-2021-251
PyPItensorflow2.2.3GHSA-8pmx-p244-g88h
PyPItensorflow-cpu2.4.2GHSA-8pmx-p244-g88h
PyPItensorflow-cpu2.1.4GHSA-8pmx-p244-g88h
PyPItensorflow-cpu2.2.3GHSA-8pmx-p244-g88h
PyPItensorflow-cpu2.3.3GHSA-8pmx-p244-g88h
PyPItensorflow-cpu2.1.4, 2.2.3, 2.3.3, 2.4.2PYSEC-2021-542
PyPItensorflow-gpu2.3.3GHSA-8pmx-p244-g88h
PyPItensorflow-gpu2.4.2GHSA-8pmx-p244-g88h
PyPItensorflow-gpu2.1.4GHSA-8pmx-p244-g88h
PyPItensorflow-gpu2.1.4, 2.2.3, 2.3.3, 2.4.2PYSEC-2021-740
PyPItensorflow-gpu2.2.3GHSA-8pmx-p244-g88h

Affected products (as reported)

VendorProductVersions
tensorflow tensorflow < 2.1.4>= 2.2.0, < 2.2.3>= 2.3.0, < 2.3.3>= 2.4.0, < 2.4.2

Weakness: CWE-665 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

References