Out-of-bounds Read in Google Tensorflow
CVE-2021-29569
TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs. The implementation(https://github.com/tensorflow/tensorflow/blob/ac328eaa3870491ababc147822cd04e91a790643/tensorflow/core/kernels/requantization_range_op.cc#L49-L50) assumes that the `input_min` and `input_max` tensors have at least one element, as it accesses the first element in two arrays. If the tensors are empty, `.flat<T>()` is an empty object, backed by an empty array. Hence, accesing even the 0th element is a read outside the bounds. 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.
Vulnerability class: Buffer Overflow
Published · last modified .
CVSS v3 metric
CVSS v3 base score 2.5 (Low). Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L.
EPSS exploit prediction
EPSS 0.002, 9.7th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Google Tensorflow
- Tensorflow — versions < 2.1.4, >= 2.2.0, < 2.2.3, >= 2.3.0, < 2.3.3
Weakness classification (CWE)
References
- github.com/tensorflow/tensorflow/security/advisories/GHSA-3h8m-483j-7xxm (Exploit, Patch, Third Party Advisory)
- github.com/tensorflow/tensorflow/commit/ef0c008ee84bad91ec6725ddc42091e19a30cf0e (Patch, Third Party Advisory)