Out-of-bounds Read in Google Tensorflow
CVE-2021-41211
TensorFlow is an open source platform for machine learning. In affected versions the shape inference code for `QuantizeV2` can trigger a read outside of bounds of heap allocated array. This occurs whenever `axis` is a negative value less than `-1`. In this case, we are accessing data before the start of a heap buffer. The code allows `axis` to be an optional argument (`s` would contain an `error::NOT_FOUND` error code). Otherwise, it assumes that `axis` is a valid index into the dimensions of the `input` tensor. If `axis` is less than `-1` then this results in a heap OOB read. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, as this version is the only one that is also affected.
Vulnerability class: Buffer Overflow
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.1 (High). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H.
EPSS exploit prediction
EPSS 0.002, 11.0th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Google Tensorflow — versions 2.6.0
- Tensorflow — versions >= 2.6.0, < 2.6.1
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (adwisatya/SnykVulndb, ARPSyndicate/cvemon). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/tensorflow/tensorflow/security/advisories/GHSA-cvgx-3v3q-m36c (Exploit, Third Party Advisory)
- github.com/tensorflow/tensorflow/commit/a0d64445116c43cf46a5666bd4eee28e7a82f244 (Patch, Third Party Advisory)